public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] Implement vFile:setfs in gdbserver
@ 2015-06-10 14:24 sergiodj+buildbot
  2015-06-10 14:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
                   ` (12 more replies)
  0 siblings, 13 replies; 1995+ messages in thread
From: sergiodj+buildbot @ 2015-06-10 14:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14d2069a321cdd2b06f1982e6832c8c5661febf4 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 14d2069a321cdd2b06f1982e6832c8c5661febf4

Implement vFile:setfs in gdbserver
This commit implements the "vFile:setfs" packet in gdbserver.

gdb/gdbserver/ChangeLog:

	* target.h (struct target_ops) <multifs_open>: New field.
	<multifs_unlink>: Likewise.
	<multifs_readlink>: Likewise.
	* linux-low.c (nat/linux-namespaces.h): New include.
	(linux_target_ops): Initialize the_target->multifs_open,
	the_target->multifs_unlink and the_target->multifs_readlink.
	* hostio.h (hostio_handle_new_gdb_connection): New declaration.
	* hostio.c (hostio_fs_pid): New static variable.
	(hostio_handle_new_gdb_connection): New function.
	(handle_setfs): Likewise.
	(handle_open): Use the_target->multifs_open as appropriate.
	(handle_unlink): Use the_target->multifs_unlink as appropriate.
	(handle_readlink): Use the_target->multifs_readlink as
	appropriate.
	(handle_vFile): Handle vFile:setfs packets.
	* server.c (handle_query): Call hostio_handle_new_gdb_connection
	after target_handle_new_gdb_connection.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: cris: use standard output helpers
@ 2016-01-02 19:11 sergiodj+buildbot
  2016-01-02 20:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-02 19:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b3fbb288afd9071523b61b3222869cfed0f95ab8 ***

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

sim: cris: use standard output helpers

The sim-io module provides output helpers, so no need to define local
ones anymore.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: convert to bfd_endian
@ 2016-01-03  5:29 sergiodj+buildbot
  2016-01-03  7:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-03  5:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ac72f0659d64d6a14da862242db0d841d2878d0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1ac72f0659d64d6a14da862242db0d841d2878d0

sim: convert to bfd_endian

Rather than re-invent endian defines, as well as maintain our own list
of OS & arch-specific includes, punt all that logic in favor of the bfd
ones already set up and maintained elsewhere.  We already rely on the
bfd library, so leveraging the endian aspect should be fine.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: nrun: use lbasename
@ 2016-01-03  9:17 sergiodj+buildbot
  2016-01-03 10:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-03  9:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aba6f46b235a3a139c04d5ed6a3310125aa9c982 ***

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

sim: nrun: use lbasename


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: use libiberty countargv in more places
@ 2016-01-03  9:29 sergiodj+buildbot
  2016-01-03 12:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-03  9:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34fed69938f1296b62354b2a825b49602fe7af50 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 34fed69938f1296b62354b2a825b49602fe7af50

sim: use libiberty countargv in more places

A bunch of places open code the countargv implementation, or outright
duplicate it (as count_argc).  Replace all of those w/countargv.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: TODO: move to wiki
@ 2016-01-04  1:04 sergiodj+buildbot
  2016-01-04  2:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-04  1:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3726f72c654ab357be5b79c78f238da7a869f9a3 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 3726f72c654ab357be5b79c78f238da7a869f9a3

sim: TODO: move to wiki

We're maintaining development docs in the wiki now:
	https://sourceware.org/gdb/wiki/Sim/TODO


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: parse_args: display getopt error ourselves
@ 2016-01-04  3:17 sergiodj+buildbot
  2016-01-04  4:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-04  3:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77cf2ef5dc9099501529151921a73be904757466 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 77cf2ef5dc9099501529151921a73be904757466

sim: parse_args: display getopt error ourselves

Fix a long standing todo where we let getopt write directly to stderr
when an invalid option is passed.  Use the sim io funcs instead as they
go through the filtered callbacks that gdb wants.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: msp430: switch to common disassembler tracing
@ 2016-01-05 20:31 sergiodj+buildbot
  2016-01-06  0:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 20:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70d394483206f5afe911fa21c8456b852c12da74 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 70d394483206f5afe911fa21c8456b852c12da74

sim: msp430: switch to common disassembler tracing

The output format is a bit different, but the new form matches all the
other trace lines.  Otherwise, it should be functionally equivalent.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix the execution of the MSP430 simulator testsuite.
@ 2016-01-05 20:37 sergiodj+buildbot
  2016-01-05 20:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 20:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 296ebfbb91bc9453134c467b4bfe8363582674f7 ***

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

Fix the execution of the MSP430 simulator testsuite.

ld	* emulparams/msp430elf.sh (RAM_START): Move to 0x500 - above the
	MSP430 hardware multiply address range.
	* scripttempl/elf32msp430.sc (__romdatastart): Define.
	(__romdatacopysize): Define.
	* scripttempl/elf32msp430_3.sc: Likewise.

tests	* testutils.inc (__pass): Use the LMA addresses of the _passmsg
	symbol.
	(__fail): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: bfin: add support disasm tracing
@ 2016-01-05 20:39 sergiodj+buildbot
  2016-01-06  2:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 20:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 824c862804128f6d31ae5f80fb741d12419da943 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 824c862804128f6d31ae5f80fb741d12419da943

sim: bfin: add support disasm tracing


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: trace: add support for disassembling
@ 2016-01-05 20:40 sergiodj+buildbot
  2016-01-05 23:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 20:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfb2629c162c05dac30fc16180953efb671c4227 ***

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

sim: trace: add support for disassembling

Some targets have started to add support for calling the disassembler
automatically when executing code.  Add support for that directly into
the trace core.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: aarch64: switch to common disassembler tracing
@ 2016-01-05 21:02 sergiodj+buildbot
  2016-01-06  3:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 21:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a846c62626357f9e966ef50917dca3a357c9644 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1a846c62626357f9e966ef50917dca3a357c9644

sim: aarch64: switch to common disassembler tracing

The output should largely be the same.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: msp430: drop duplicate sim_load_file call
@ 2016-01-05 21:27 sergiodj+buildbot
  2016-01-06  5:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 21:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 402cf0534665db83e19c00f130184e94552a75fb ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 402cf0534665db83e19c00f130184e94552a75fb

sim: msp430: drop duplicate sim_load_file call

There's no need, or desire, to call sim_load_file from sim_open.  The
higher levels (gdb/run) take care of calling sim_load for us already.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add myself as the maintainer for the AArch64.
@ 2016-01-05 21:38 sergiodj+buildbot
  2016-01-05 22:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 21:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4eb70007f1a750b5bdf4e2a08eef96cf7c666c0a ***

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

Add myself as the maintainer for the AArch64.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: score: drop sim file check
@ 2016-01-05 22:13 sergiodj+buildbot
  2016-01-06  6:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 22:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6675033211e145ecd094b6803ed4a3427b3fd21e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6675033211e145ecd094b6803ed4a3427b3fd21e

gdb: score: drop sim file check

There has never been a GNU/sim port for the S+Core architecture.
It was added to support private code that has (and most likely
never will) see the light of day [1].  Punt this as we don't do
this for other people.  If you want to maintain a proprietary
internal build, then that's not really our problem.

[1] https://sourceware.org/ml/gdb-patches/2009-03/msg00390.html


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] libiberty: fix warnings about left shifting a negative value.
@ 2016-01-05 22:21 sergiodj+buildbot
  2016-01-06  8:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 22:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13b356b2b5c1857490b7911dbbb48e17a3a92b04 ***

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

libiberty: fix warnings about left shifting a negative value.

  GCC PR 66827 reports some problems with left shifting a negative
  value:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66827

  Of the problems reported only two remain - in libiberty/regex.c:

libiberty/regex.c:6970:11: runtime error: left shift of negative value -1
libiberty/regex.c:7165:4: runtime error: left shift of negative value -1

  The patch below fixes these errors by casting the value to be shifted
  to unsigned before the shift occurs.

  No regressions were found in the libiberty testsuite or bootstrapping
  gcc (on an x86_64 target).


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] libiberty: Tweak the documentation of libiberty's xcrc32 function
@ 2016-01-05 22:29 sergiodj+buildbot
  2016-01-06  9:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 22:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4bec0ef03e91506caf60d8842786b29c2d2ff049 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 4bec0ef03e91506caf60d8842786b29c2d2ff049

libiberty: Tweak the documentation of libiberty's xcrc32 function

In some places the xcrc32 documentation refers to GDB's own crc32
implementation, but GDB no longer has its own crc32 implementation.
It now uses libiberty's xcrc32 throughout.  So this patch removes
these references to GDB's now-nonexistent crc32 implementation.

Also, there appears to be a bug in the table-generation program embedded
within the documentation.  When the variable "int i" is >= 128, the
computation "i << 24" shifts a one bit into the sign bit (assuming a
32-bit int), which is UB.  To avoid this UB, I think it is sufficient to
make the induction variables i and j have type unsigned int.  This bug
seems latent, however.  I ran the program before and after this change
and the table output is the same.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] libiberty: {count, dup, write}argv: constify argv input slightly
@ 2016-01-05 23:03 sergiodj+buildbot
  2016-01-06 12:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 23:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b36c1ccb1feb678f7279b4a8d66c0125d4295078 ***

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

libiberty: {count,dup,write}argv: constify argv input slightly

Would be more useful if we could use "const char * const *", but there's
a long standing bug where gcc warns about incompatible pointers when you
try to pass in "char **".  We can at least constify the array itself as
gcc will not warn in that case.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] libiberty: dupargv: rewrite to use xstrdup
@ 2016-01-05 23:23 sergiodj+buildbot
  2016-01-06 10:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 23:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 203217665139943a4f0d1797b9a5f913b3acf184 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 203217665139943a4f0d1797b9a5f913b3acf184

libiberty: dupargv: rewrite to use xstrdup

This func is basically open coding the xstrdup function, so gut it
and use it directly.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: change version stamp to git
@ 2016-01-06  4:40 sergiodj+buildbot
  2016-01-06 13:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-06  4:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf69ad5a189db1dca362723a3b0a7a1b545219a9 ***

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

gdb: change version stamp to git


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Change copyright owner to FSF in sim/testsuite/sim/mips/hilo-hazard-4.s
@ 2016-01-06  5:52 sergiodj+buildbot
  2016-01-06 14:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-06  5:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68477034727ad85aeed248ec995da746f7639e53 ***

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

Change copyright owner to FSF in sim/testsuite/sim/mips/hilo-hazard-4.s

sim/testsuite/sim/mips/ChangeLog:

        * hilo-hazard-4.s: Change copyright ownder to FSF.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdb.python/py-infthread.exp test message typo
@ 2016-01-06 11:46 sergiodj+buildbot
  2016-01-06 16:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79bc59cb349fdbb8d3fa81804eb121af3c340c22 ***

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

Fix gdb.python/py-infthread.exp test message typo

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

	* gdb.python/py-infthread.exp: Fix typo.  Expect t0.num to be 1.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] bfd/arc: Add R_ prefix to all relocation names
@ 2016-01-06 14:28 sergiodj+buildbot
  2016-01-06 17:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 14:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b05a65d0adb340e4129f62c1d380a09935ee433d ***

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

bfd/arc: Add R_ prefix to all relocation names

The convention within for relocation names is that they start with the
string "R_", however, this is not so for ARC for the display names of
relocations, however, internally, the names for the relocations types do
have the 'R_' prefix.  I suspect that the missing 'R_' on the output
strings was an oversight, as I can't see any comment to the contrary.

To bring ARC into line with other targets, this commit adds the 'R_'
prefix to the output strings used for relocation names, and updates all
of the assembler tests where this was exposed.

bfd/ChangeLog:

	* elf32-arc.c (reloc_type_to_name): Change ARC_RELOC_HOWTO to
	place 'R_' before the reloc name returned.
	(elf_arc_howto_table): Change ARC_RELOC_HOWTO to place 'R_' before
	the relocation string.

gas/ChangeLog:

	* testsuite/gas/arc/adc.d: Add 'R_' prefix to relocation names.
	* testsuite/gas/arc/add.d: Likewise.
	* testsuite/gas/arc/and.d: Likewise.
	* testsuite/gas/arc/asl.d: Likewise.
	* testsuite/gas/arc/asr.d: Likewise.
	* testsuite/gas/arc/bic.d: Likewise.
	* testsuite/gas/arc/extb.d: Likewise.
	* testsuite/gas/arc/extw.d: Likewise.
	* testsuite/gas/arc/j.d: Likewise.
	* testsuite/gas/arc/jl.d: Likewise.
	* testsuite/gas/arc/ld2.d: Likewise.
	* testsuite/gas/arc/lsr.d: Likewise.
	* testsuite/gas/arc/mov.d: Likewise.
	* testsuite/gas/arc/or.d: Likewise.
	* testsuite/gas/arc/pcl-relocs.d: Likewise.
	* testsuite/gas/arc/pcrel-relocs.d: Likewise.
	* testsuite/gas/arc/pic-relocs.d: Likewise.
	* testsuite/gas/arc/plt-relocs.d: Likewise.
	* testsuite/gas/arc/rlc.d: Likewise.
	* testsuite/gas/arc/ror.d: Likewise.
	* testsuite/gas/arc/rrc.d: Likewise.
	* testsuite/gas/arc/sbc.d: Likewise.
	* testsuite/gas/arc/sda-relocs.d: Likewise.
	* testsuite/gas/arc/sda-relocs2.d: Likewise.
	* testsuite/gas/arc/sexb.d: Likewise.
	* testsuite/gas/arc/sexw.d: Likewise.
	* testsuite/gas/arc/st.d: Likewise.
	* testsuite/gas/arc/sub.d: Likewise.
	* testsuite/gas/arc/tls-relocs.d: Likewise.
	* testsuite/gas/arc/xor.d: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM/AArch64] Fix -Werror=unused-const-variable warnings in GDBserver
@ 2016-01-06 15:10 sergiodj+buildbot
  2016-01-06 18:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2ca446f682854c2b187178358b97174bf313fa7 ***

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

[ARM/AArch64] Fix -Werror=unused-const-variable warnings in GDBserver

This patch fixes gcc warning when build ARM GDBserver and AArch64
GDBserver,

AArch64 GDBserver:

gdb/gdbserver/linux-aarch32-low.h:36:29: error: 'thumb2_breakpoint' defined but not used [-Werror=unused-const-variable]
 static const unsigned short thumb2_breakpoint[] = { 0xf7f0, 0xa000 };
                             ^
gdb/gdbserver/linux-aarch32-low.h:34:29: error: 'thumb_breakpoint' defined but not used [-Werror=unused-const-variable]
 static const unsigned short thumb_breakpoint = 0xde01;
                             ^
gdb/gdbserver/linux-aarch32-low.h:28:28: error: 'arm_breakpoint' defined but not used [-Werror=unused-const-variable]
 static const unsigned long arm_breakpoint = arm_eabi_breakpoint;
                            ^
cc1: all warnings being treated as errors

ARM GDBserver:

gdb/gdbserver/linux-aarch32-low.h:34:29: error: 'thumb_breakpoint' defined but not used [-Werror=unused-const-variable]
 static const unsigned short thumb_breakpoint = 0xde01;
                             ^~~~~~~~~~~~~~~~

gdb/gdbserver/linux-aarch32-low.h:28:28: error: 'arm_breakpoint' defined but not used [-Werror=unused-const-variable]
 static const unsigned long arm_breakpoint = arm_eabi_breakpoint;
                            ^~~~~~~~~~~~~~

by simply moving these macros and variables to
linux-aarch32-low.c and only declare thumb2_breakpoint in
linux-aarch32-low.h, which is not perfect, and reveals some issues
in recent arm GDBserver software single step changes.  I'll post
follow-up patches.

gdb/gdbserver:

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

	* linux-aarch32-low.h (arm_abi_breakpoint): Move to
	linux-aarch32-low.c.
	(arm_eabi_breakpoint, arm_breakpoint): Likewise.
	(arm_breakpoint_len, thumb_breakpoint_len): Likewise.
	(thumb2_breakpoint, thumb2_breakpoint_len): Likewise.
	(thumb2_breakpoint): Declare.
	* linux-aarch32-low.c (arm_abi_breakpoint): Moved from
	linux-aarch32-low.h.
	(arm_eabi_breakpoint, arm_breakpoint): Likewise.
	(arm_breakpoint_len, thumb_breakpoint_len): Likewise.
	(thumb2_breakpoint, thumb2_breakpoint_len): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Make {arm,thumb}_get_next_pcs_raw static
@ 2016-01-06 15:34 sergiodj+buildbot
  2016-01-06 20:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5aa306929127aacf9890a949f9a21b38a0e0e7e ***

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

Make {arm,thumb}_get_next_pcs_raw static

This patch makes arm_get_next_pcs_raw and thumb_get_next_pcs_raw
static.

gdb:

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

	* arch/arm-get-next-pcs.c (arm_get_next_pcs): Move it to some
	lines below.
	(thumb_get_next_pcs_raw): Make it static.
	(arm_get_next_pcs_raw): Likewise.
	* arch/arm-get-next-pcs.h (thumb_get_next_pcs_raw): Remove the
	declaration.
	(arm_get_next_pcs_raw): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes
@ 2016-01-06 18:52 sergiodj+buildbot
  2016-01-06 21:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 18:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b31e4803316aa0635a6f9beaeceea3e18dbbe459 ***

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

MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes

	include/
	* opcode/mips.h: Add a summary of MIPS16 operand codes.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: sim_{create_inferior, open, parse_args}: constify argv/env slightly
@ 2016-01-07  2:58 sergiodj+buildbot
  2016-01-07  4:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-07  2:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e3d4f4d5d386995e99d035354a9e411d1dc0331 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 2e3d4f4d5d386995e99d035354a9e411d1dc0331

sim: sim_{create_inferior,open,parse_args}: constify argv/env slightly

2016-01-03  Mike Frysinger  <vapier@gentoo.org>

	* sim-options.c (sim_parse_args): Mark argv array const.
	* sim-options.h (sim_parse_args): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: config: drop use of __DATE__/__TIME__
@ 2016-01-07  3:07 sergiodj+buildbot
  2016-01-07  5:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-07  3:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b900245c3b92fc460a3f7fa17d14eb08f9ab4c76 ***

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

sim: config: drop use of __DATE__/__TIME__

These don't add a whole lot of useful info, and people don't like them as
it makes builds unreproducible, so just drop them.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS: Complete `status' to `err' renaming in `mips_breakpoint_from_pc'
@ 2016-01-07 19:37 sergiodj+buildbot
  2016-01-07 20:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-07 19:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5dd0563088b3ca9f5fd66daa0ffe823b60e4b92e ***

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

MIPS: Complete `status' to `err' renaming in `mips_breakpoint_from_pc'

Complement commit d09f2c3f [target_read_memory&co: no longer return
target_xfer_status] and apply the same change made to the big-endian leg
of the function to the little-endian leg as well.

	gdb/
	* mips-tdep.c (mips_breakpoint_from_pc): Rename local `status'
	to `err' in the little-endian leg.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE
@ 2016-01-08  9:58 sergiodj+buildbot
  2016-01-08 11:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-08  9:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 109575d7ebac21a0eb67980001ecd4173d696f88 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 109575d7ebac21a0eb67980001ecd4173d696f88

[ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE

2016-01-08  Richard Sandiford  <richard.sandiford@arm.com>
	    Jiong Wang  <jiong.wang@arm.com>

	PR ld/19368
	bfd/
	* elf32-arm.c (elf32_arm_reloc_type_class): Map R_ARM_IRELATIVE to
	reloc_class_ifunc.

	ld/
	* testsuite/ld-arm/ifunc-3.rd: Update expected result.
	* testsuite/ld-arm/ifunc-4.rd: Likewise.
	* testsuite/ld-arm/ifunc-9.rd: Likewise.
	* testsuite/ld-arm/ifunc-10.rd: Likewise.
	* testsuite/ld-arm/ifunc-12.rd: Likewise.
	* testsuite/ld-arm/ifunc-13.rd: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] m68k: fix constraints of move.[bw] for ISA_B/C
@ 2016-01-08 10:52 sergiodj+buildbot
  2016-01-08 12:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 10:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 83c3256ef5afe10625fd55dda2df5fc56b9b7393 ***

Author: Andreas Schwab <schwab@linux-m68k.org>
Branch: master
Commit: 83c3256ef5afe10625fd55dda2df5fc56b9b7393

m68k: fix constraints of move.[bw] for ISA_B/C

For ISA_B/C only the combination #,d(An) is allowed in addition to the
ISA_A combinations for move.b and move.w (and pc-relative is never
allowed as destination).

opcodes/
	PR gas/13050
	* m68k-opc.c (moveb, movew): For ISA_B/C only allow #,d(An) in
	addition to ISA_A.

gas/
	PR gas/13050
	* testsuite/gas/m68k/all.exp: Add tests p13050-1 and p13050-2.
	* testsuite/gas/m68k/p13050-1.s: New file.
	* testsuite/gas/m68k/p13050-2.d: New file.
	* testsuite/gas/m68k/p13050-2.s: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Check input interrupt first when reading packet
@ 2016-01-08 11:16 sergiodj+buildbot
  2016-01-08 13:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 11:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5a0dd67a459338efb77f8d82bb3650d801ff0dd5 ***

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

Check input interrupt first when reading packet

Hi,
I see timeout in one of several runs of random-signal.exp like this,

 $ (set -e; while true; do make check RUNTESTFLAGS="--target_board=native-gdbserver random-signal.exp"; done)

In about every five runs, we can see a fail,

PASS: gdb.base/random-signal.exp: continue
^CFAIL: gdb.base/random-signal.exp: stop with control-c (timeout)

after some investigation, I find '\003' may be discarded by GDBserver when
it is expecting '$'.  In GDB side, both normal packets and '\003' are sent
via function send, but GDBserver may receive them at any time, that is to
say, in the receive buffer in GDBserver, '\003' may appear before or after
normal packet.  However, current GDBserver doesn't handle this case.

With this patch applied, I don't see this fail in multiple runs.
Although there is still timeout fail, that is a different problem, the
next patch will fix it.

gdb/gdbserver:

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

	* remote-utils.c (getpkt): If c is '\003', call target hook
	request_interrupt.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Change SIGINT handler for extension languages only when target terminal is ours
@ 2016-01-08 11:25 sergiodj+buildbot
  2016-01-08 15:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f99e8fc9cb84ca80cfca6c119f1f22bbfd2a314 ***

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

Change SIGINT handler for extension languages only when target terminal is ours

I see a timeout in gdb.base/random-signal.exp,

 Continuing.^M
 PASS: gdb.base/random-signal.exp: continue
 ^CPython Exception <type 'exceptions.KeyboardInterrupt'> <type
 exceptions.KeyboardInterrupt'>: ^M
 FAIL: gdb.base/random-signal.exp: stop with control-c (timeout)

it can be reproduced by running random-signal.exp with native-gdbserver
in a loop, like this, and the fail will be shown in about 20 runs,

$ (set -e; while true; do make check RUNTESTFLAGS="--target_board=native-gdbserver random-signal.exp"; done)

In the test, the program is being single-stepped for software watchpoint,
and in each internal stop, python unwinder sniffer is used,

 #0  pyuw_sniffer (self=<optimised out>, this_frame=<optimised out>, cache_ptr=0xd554f8) at /home/yao/SourceCode/gnu/gdb/git/gdb/python/py-unwind.c:608
 #1  0x00000000006a10ae in frame_unwind_try_unwinder (this_frame=this_frame@entry=0xd554e0, this_cache=this_cache@entry=0xd554f8, unwinder=0xecd540)
     at /home/yao/SourceCode/gnu/gdb/git/gdb/frame-unwind.c:107
 #2  0x00000000006a143f in frame_unwind_find_by_frame (this_frame=this_frame@entry=0xd554e0, this_cache=this_cache@entry=0xd554f8)
     at /home/yao/SourceCode/gnu/gdb/git/gdb/frame-unwind.c:163
 #3  0x000000000069dc6b in compute_frame_id (fi=0xd554e0) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:454
 #4  get_prev_frame_if_no_cycle (this_frame=this_frame@entry=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1781
 #5  0x000000000069fdb9 in get_prev_frame_always_1 (this_frame=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1955
 #6  get_prev_frame_always (this_frame=this_frame@entry=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1971
 #7  0x00000000006a04b1 in get_prev_frame (this_frame=this_frame@entry=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:2213

when GDB goes to python extension, or other language extension, the
SIGINT handler is changed, and is restored when GDB leaves extension
language.  GDB only stays in extension language for a very short period
in this case, but if ctrl-c is pressed at that moment, python extension
will handle the SIGINT, and exceptions.KeyboardInterrupt is shown.

Language extension is used in GDB side rather than inferior side,
so GDB should only change SIGINT handler for extension language when
the terminal is ours (not inferior's).  This is what this patch does.
With this patch applied, I run random-signal.exp in a loop for 18
hours, and no fail is shown.

gdb:

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

	* extension.c: Include target.h.
	(set_active_ext_lang): Only call install_gdb_sigint_handler,
	check_quit_flag, and set_quit_flag if target_terminal_is_ours
	returns false.
	(restore_active_ext_lang): Likewise.
	* target.c (target_terminal_is_ours): New function.
	* target.h (target_terminal_is_ours): Declare.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] perf testsuite: python 3 fixes
@ 2016-01-08 15:34 sergiodj+buildbot
  2016-01-08 16:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 582a1b0064b14cb12b18f48678876d32c59c11c8 ***

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

perf testsuite: python 3 fixes

There are a few errors when trying to run the performance testsuite with
Python 3.  This commit fixes them.

In Python 2, it was possible to use relative imports (importing a module
relative to the current one).  In Python 3 it isn't.  So I use
absolute_import from the __future__ module, which allows Python 2 to
behave like Python 3, and use the Python 3 syntax.

In Python 3, dict.iterkeys doesn't exist anymore.  Using dict.keys is a
good compromise in this case.

gdb/testsuite/ChangeLog:

	* gdb.perf/lib/perftest/perftest.py: Change relative imports to
	absolute.
	(SingleStatisticTestResult.report): Use dict.keys instead of
	dict.iterkeys.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdb.multi/base.exp testsuite regression
@ 2016-01-08 19:16 sergiodj+buildbot
  2016-01-08 20:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 19:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cfc1fcb515d1ecd8445905b4749b81b3ca69552 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 6cfc1fcb515d1ecd8445905b4749b81b3ca69552

Fix gdb.multi/base.exp testsuite regression

Regressed by:

commit 762f774785f4ef878ac4c831e1f4733dc957234d
Author: Pedro Alves <palves@redhat.com>
Date:   Thu Dec 10 16:21:06 2015 +0000
    Stop using nowarnings in gdb/testsuite/gdb.multi/

+gdb compile failed, gdb/testsuite/gdb.multi/hello.c: In function 'commonfun':
+gdb/testsuite/gdb.multi/hello.c:24:19: warning: implicit declaration of function 'bar' [-Wimplicit-function-declaration]
+ int commonfun() { bar(); } /* from hello */
+                   ^
+gdb/testsuite/gdb.multi/hello.c: At top level:
+gdb/testsuite/gdb.multi/hello.c:26:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ bar()
+ ^
+gdb/testsuite/gdb.multi/hello.c:32:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ hello(int x)
+ ^
+gdb/testsuite/gdb.multi/hello.c:38:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ main()
+ ^
+UNTESTED: gdb.multi/base.exp: base.exp

gdb/testsuite/ChangeLog
2016-01-08  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.multi/goodbye.c: Fix compilation warnings by adding return types
	and reordering the functions.
	* gdb.multi/hangout.c: Likewise.
	* gdb.multi/hello.c: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: drop common/cconfig.h in favor of a single config.h
@ 2016-01-09  9:01 sergiodj+buildbot
  2016-01-09 10:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-09  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 936df7568a0e47547285a0dd57b81643264fef38 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 936df7568a0e47547285a0dd57b81643264fef38

sim: drop common/cconfig.h in favor of a single config.h

The common subdir sets up a cconfig.h file to hold checks for the common
code.  In practice, most files still end up using config.h instead which
just leads to confusion.

Merge all the configure checks that went into cconfig.h into SIM_AC_COMMON
so we can drop the cconfig.h file altogether.  Now there is only a single
config.h file like normal.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: stop configuring common subdir
@ 2016-01-09  9:24 sergiodj+buildbot
  2016-01-09 11:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-09  9:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5295724cdc94a09713b021728b02163dad128e9e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5295724cdc94a09713b021728b02163dad128e9e

sim: stop configuring common subdir

Now that cconfig.h doesn't exist, there's no need to build in the common
subdir anymore.  We leave the configure/Makefile files in there as there
is a helper for developers to generate the nltvals.def file.  Once that
gets cleaned up in the future though, we can drop the build logic too.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: drop --enable-sim-cflags option
@ 2016-01-10  8:17 sergiodj+buildbot
  2016-01-10  9:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-10  8:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22be3fbeaccf50e3c0f58d0f7e9f7ed77effeaab ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 22be3fbeaccf50e3c0f58d0f7e9f7ed77effeaab

sim: drop --enable-sim-cflags option

No other sub directory provides such a configuration option, so
drop it from the sim dir as well.  This cleans up a good bit of
code in the process.

If people want to use custom flags for just the sim, they can
still run configure+make by hand in the sim subdir and use the
normal CFLAGS settings.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: drop --enable-sim-{regparm,stdcall} options
@ 2016-01-10  8:33 sergiodj+buildbot
  2016-01-10 10:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-10  8:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0dc73ef7c304e6ffc9ce43b2131c77553a74e1d4 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 0dc73ef7c304e6ffc9ce43b2131c77553a74e1d4

sim: drop --enable-sim-{regparm,stdcall} options

These options were never exposed for most sims (just the ppc one),
and they are really only useful on 32-bit x86 systems.  Considering
modern systems tend to be 64-bit x86_64 and how well modern compilers
are at optimizing code, these have outlived their usefulness.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: allow the inline configure option everywhere
@ 2016-01-10  8:51 sergiodj+buildbot
  2016-01-10 12:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-10  8:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 347fe5bb868b7383d4f6942894b31ecf1da6894e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 347fe5bb868b7383d4f6942894b31ecf1da6894e

sim: allow the inline configure option everywhere

Currently ports have to call SIM_AC_OPTION_INLINE explicitly in order
to make the configure flag available.  There's no real reason to not
allow this flag for all ports, so move it to the common sim macro.
This way we get standard behavior across all ports too.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: mips: drop SIM_AC_OPTION_SMP call
@ 2016-01-10  8:59 sergiodj+buildbot
  2016-01-10 13:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-10  8:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d90347b5dcbb10ecb410b1246613c0caf511bd9 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6d90347b5dcbb10ecb410b1246613c0caf511bd9

sim: mips: drop SIM_AC_OPTION_SMP call

No other port calls this macro directly, and mips has it hardcoded
to the default -- disabling smp.  In the future we'll enable this
for all targets in common code, so tidy up the mips code now.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: drop targ-vals.def->nltvals.def indirection
@ 2016-01-10  9:12 sergiodj+buildbot
  2016-01-10 14:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-10  9:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99d8e879938c947588332a9cc579d378ccc2a855 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 99d8e879938c947588332a9cc579d378ccc2a855

sim: drop targ-vals.def->nltvals.def indirection

We don't have alternative nltvals.def files, so always symlinking
the targ-vals.def file to it doesn't gain us anything.  It does
make the build more complicated though and a pain to convert to
something newer (like automake).  Drop the symlinking entirely.

In the future, we'll want to explode this file anyways into the
respective arch dirs so things can be selected dynamically at
runtime, so it's not like we'll be bringing this back.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: allow the assert configure option everywhere
@ 2016-01-10 22:20 sergiodj+buildbot
  2016-01-10 23:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-10 22:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35656e95217a20309c0a0f16bf0c89a49a549177 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 35656e95217a20309c0a0f16bf0c89a49a549177

sim: allow the assert configure option everywhere

Currently ports have to call SIM_AC_OPTION_ASSERT explicitly in order
to make the configure flag available, which none of them do.  There's
no real reason to not allow this flag for all ports, so move it to the
common sim macro.  This way we get standard behavior across all ports.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: allow the environment configure option everywhere
@ 2016-01-10 22:28 sergiodj+buildbot
  2016-01-11  0:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-10 22:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16f7876d71604f835aefe48f0bf230c028c05d99 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 16f7876d71604f835aefe48f0bf230c028c05d99

sim: allow the environment configure option everywhere

Currently ports have to call SIM_AC_OPTION_ENVIRONMENT explicitly in
order to make the configure flag available.  There's no real reason
to not allow this flag for all ports, so move it to the common sim
macro.  This way we get standard behavior across all ports too.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: drop unused SIM_AC_OPTION_PACKAGES
@ 2016-01-10 23:15 sergiodj+buildbot
  2016-01-11  2:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-10 23:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e19418e02e25ae4c62eb95547220897fa6aaf2e0 ***

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

sim: drop unused SIM_AC_OPTION_PACKAGES

This was imported from the ppc sim, but that was only used to control
a single file, and that is already governed by the hw models.  There's
no need to have a sep configure option here, especially since none of
the other sims are using it.  Even when the code is enabled, there's
no runtime overhead.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: move many common settings from CPPFLAGS to config.h
@ 2016-01-11  0:08 sergiodj+buildbot
  2016-01-11  3:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-11  0:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce39bd389039d99458950b072550ab52f0a07a34 ***

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

sim: move many common settings from CPPFLAGS to config.h

Rather than stuffing the command line with a bunch of -D flags, start
moving things to config.h which is managed by autoheader.  This makes
the makefile a bit simpler and the build output tighter, and it makes
the migration to automake easier as there are fewer vars to juggle.

We'll want to move the other options out too, but it'll take more work.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: config: do not try to align settings
@ 2016-01-11  6:11 sergiodj+buildbot
  2016-01-11  7:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-11  6:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34ac507d94ea4af59f931b26e66e7721c967f55c ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 34ac507d94ea4af59f931b26e66e7721c967f55c

sim: config: do not try to align settings

We try to align the output for a few settings, but not most of them.
Drop the aligning entirely to be lazy.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Import changes made to files shared with the FSF GCC project.
@ 2016-01-11 11:18 sergiodj+buildbot
  2016-01-11 12:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 11:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4849dfd8f454b9c595e6ee7477f6b7b25c31a499 ***

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

Import changes made to files shared with the FSF GCC project.

	Import the following changes from the GCC mainline:

	2015-11-13  Tsvetkova Alexandra  <aleksandra.tsvetkova@intel.com>

	* configure.ac: Enable libmpx by default.
	* configure: Regenerated.

	2015-11-19  Martin Liska  <mliska@suse.cz>

	* .gitignore: Add .clang-format to ignored files.
	* Makefile.tpl: Add clang-format.
	* Makefile.in: Regenerate.

	2015-12-01  Andreas Tobler  <andreast@gcc.gnu.org>

	PR libffi/65726
	* Makefile.def (lang_env_dependencies): Make libffi depend
	on cxx.
	* Makefile.in: Regenerate.

	2015-12-02  Ian Lance Taylor  <iant@google.com>

	PR go/66147
	* Makefile.tpl (HOST_EXPORTS): Add XGCC_FLAGS_FOR_TARGET.
	* Makefile.in: Regenerate.

	2015-12-17  Nathan Sidwell  <nathan@acm.org>

	* config/isl.m4 (ISL_CHECK_VERSION): Add gmp libs.
	* configure: Regenerate.

	2015-12-17  Sebastian Pop  <s.pop@samsung.com>

	* Makefile.in: Replace ISL with isl.
	* Makefile.tpl: Same.
	* config/isl.m4: Same.
	* configure.ac: Same.
	* contrib/download_prerequisites: Same.
	* configure: Regenerate.

	2016-01-01  Ben Elliston  <bje@gnu.org>

	* config.guess: Import version 2016-01-01.
	* config.sub: Likewise.

include	2016-01-07  Mike Frysinger  <vapier@gentoo.org>

	* longlong.h: Change !__SHMEDIA__ to
	(!defined (__SHMEDIA__) || !__SHMEDIA__).
	Change __SHMEDIA__ to defined (__SHMEDIA__) && __SHMEDIA__.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Delete opcodes that have been removed from ISA 3.0.
@ 2016-01-11 18:06 sergiodj+buildbot
  2016-01-11 19:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 18:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afa8d4054b8e0b1384f2d07f1c15163c0699d660 ***

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

Delete opcodes that have been removed from ISA 3.0.

opcodes/
	* ppc-opc.c <xscmpnedp>: Delete.
	<xvcmpnedp>: Likewise.
	<xvcmpnedp.>: Likewise.
	<xvcmpnesp>: Likewise.
	<xvcmpnesp.>: Likewise.

gas/
	* testsuite/gas/ppc/power9.d <xscmpnedp, xvcmpnedp, xvcmpnedp.,
	xvcmpnesp, xvcmpnesp.>: Delete tests.
	* testsuite/gas/ppc/power9.s: Likewise.
	* testsuite/gas/ppc/vsx3.d: Likewise.
	* testsuite/gas/ppc/vsx3.s: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: split out warnings helpers
@ 2016-01-11 19:13 sergiodj+buildbot
  2016-01-11 20:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b835bb5265d614fd8a4759f284b987b365292c36 ***

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

gdb: split out warnings helpers

This will allow the sim tree to use the same set of warnings.
The new code in warning.m4 is exactly the same (other than the
AC_DEFUN wrapping).


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Fix false FAILs on too long base directory
@ 2016-01-11 21:16 sergiodj+buildbot
  2016-01-11 22:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0ecb95f3dc0c3e8d1545f0a37c0c3e537e1ea96 ***

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

testsuite: Fix false FAILs on too long base directory

I was getting

gu (print arg0)^M
= 0x7fffffffdafb
"/unsafebuild-x86_64-redhat-linux-gnu/gdb/testsuite.unix.-m64/outputs/gdb.guile/scm-value/scm-"...^M
(gdb) FAIL: gdb.guile/scm-value.exp: verify dereferenced value
python print (arg0)^M
0x7fffffffdafd
"/unsafebuild-x86_64-redhat-linux-gnu/gdb/testsuite.unix.-m64/outputs/gdb.python/py-value/py-v"...^M
(gdb) FAIL: gdb.python/py-value.exp: verify dereferenced value

and also:

(gdb) p argv[0]^M
$2 = 0x7fffffffd832 "/home/jkratoch/redhat/gdb-test-", 'x' <repeats 169
times>...^M
(gdb) FAIL: gdb.guile/scm-value.exp: argv[0] should be available on this
target

gdb/testsuite/ChangeLog
2016-01-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.guile/scm-value.exp (test_value_in_inferior): Set print elements
	and repeats to unlimited.
	* gdb.python/py-value.exp: Likewise.
	* lib/gdb.exp (gdb_has_argv0): Save and temporarily set print elements
	and repeats to unlimited.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Regression for foll-vfork.exp
@ 2016-01-11 21:25 sergiodj+buildbot
  2016-01-11 23:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 21:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a70630256e21a7b86344d555dbe39407e998f91 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 9a70630256e21a7b86344d555dbe39407e998f91

testsuite: Regression for foll-vfork.exp

fe33faff35a8ee19db823149e764e3373e603bb9 is the first bad commit
commit fe33faff35a8ee19db823149e764e3373e603bb9
Author: Simon Marchi <simon.marchi@ericsson.com>
Date:   Tue Dec 22 10:52:31 2015 -0500
    Remove HP-UX reference in foll-vfork.exp

FAIL: gdb.base/foll-vfork.exp: exec: vfork parent follow, finish after tcatch vfork: continue to vfork
FAIL: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: continue to vfork
FAIL: gdb.base/foll-vfork.exp: exit: vfork parent follow, finish after tcatch vfork: continue to vfork
FAIL: gdb.base/foll-vfork.exp: exit: vfork child follow, finish after tcatch vfork: continue to vfork

It happens for plain gdb.base/foll-vfork.exp runtest on Fedora 23 x86_64.

-Temporary catchpoint 2 (vforked process 24562), vfork () at ../sysdeps/unix/sysv/linux/x86_64/vfork.S:52^M
+Temporary catchpoint 2 (vforked process 25345), vfork () at ../sysdeps/unix/sysv/linux/x86_64/vfork.S:52^M
 52             pushq   %rdi^M
 Current language:  auto^M
 The current source language is "auto; currently asm".^M
-(gdb) PASS: gdb.base/foll-vfork.exp: exec: vfork parent follow, finish after tcatch vfork: continue to vfork
+(gdb) FAIL: gdb.base/foll-vfork.exp: exec: vfork parent follow, finish after tcatch vfork: continue to vfork

-Temporary catchpoint 2 (vforked process 24629), vfork () at ../sysdeps/unix/sysv/linux/x86_64/vfork.S:52^M
+Temporary catchpoint 2 (vforked process 25411), vfork () at ../sysdeps/unix/sysv/linux/x86_64/vfork.S:52^M
 52             pushq   %rdi^M
 Current language:  auto^M
 The current source language is "auto; currently asm".^M
-(gdb) PASS: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: continue to vfork
+(gdb) FAIL: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: continue to vfork

So I have reverted it and just simplified the comment.

The third case is not necessary during testing but I have changed back all the
3 cases.

Pedro Alves:
I know it was that way before, but would you mind moving this to a helper
proc.

gdb/testsuite/ChangeLog
2016-01-11  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	* gdb.base/foll-vfork.exp (tcatch_vfork_then_parent_follow)
	(tcatch_vfork_then_child_follow_exec)
	(tcatch_vfork_then_child_follow_exit): Revert back DWARF vfork
	identification.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: i386 regression for funcargs.exp
@ 2016-01-11 21:31 sergiodj+buildbot
  2016-01-12  1:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 21:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01d8c27e4f77375c0e157d115266129b76ff6734 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 01d8c27e4f77375c0e157d115266129b76ff6734

testsuite: i386 regression for funcargs.exp

3ca22649a6dfeb71058c33be4d0542b98f1f0ff5 is the first bad commit
commit 3ca22649a6dfeb71058c33be4d0542b98f1f0ff5
Author: Simon Marchi <simon.marchi@polymtl.ca>
Date:   Mon Dec 21 12:51:54 2015 -0500
    Remove HP-UX references fom testsuite
@@ -1013,13 +1013,6 @@ proc localvars_in_indirect_call { } {
     #

     gdb_test_multiple "finish" "finish from indirectly called function" {
-       -re "\\(\\*pointer_to_call0a\\) \\(c, s, i, l\\);.*First.*$gdb_prompt $" {
-           #On hppa2.0w-hp-hpux11.00, gdb finishes at one line earlier than
-           #hppa1.1-hp-hpux11.00. Therefore, an extra "step" is necessary
-           #to continue the test.
-           send_gdb "step\n"
-           exp_continue
-	}
        -re ".*\\(\\*pointer_to_call0a\\) \\(c, s, i, l\\);.*Second.*$gdb_prompt $" {
            pass "finish from indirectly called function"
       	}

->

 finish^M
 Run till exit from #0  call0a (c=97 'a', s=1, i=2, l=3) at ./gdb.base/funcargs.c:82^M
 0x0804a189 in main () at ./gdb.base/funcargs.c:583^M
 583	  (*pointer_to_call0a) (c, s, i, l);    /* First step into call0a.  */^M
-(gdb) step^M
-584	  (*pointer_to_call0a) (c, s, i, l);    /* Second step into call0a.  */^M
-(gdb) PASS: gdb.base/funcargs.exp: finish from indirectly called function
+(gdb) FAIL: gdb.base/funcargs.exp: finish from indirectly called function
 step^M
-call0a (c=97 'a', s=1, i=2, l=3) at ./gdb.base/funcargs.c:82^M
-82	  c = 'a';^M
-(gdb) PASS: gdb.base/funcargs.exp: stepping into indirectly called function
+584	  (*pointer_to_call0a) (c, s, i, l);    /* Second step into call0a.  */^M
+(gdb) FAIL: gdb.base/funcargs.exp: stepping into indirectly called function

At least on x86_64 with testsuite in -m32 (expecting native i386 would be the
same).

Pedro Alves:

The difference is that with newer GCC there's an extra instruction
after the call which is still assigned to line 583:

$ diff -up /tmp/4.8.3 /tmp/6.0.0 -U 1000
--- /tmp/4.8.3  2016-01-11 12:37:39.611089156 +0000
+++ /tmp/6.0.0  2016-01-11 13:21:00.021127976 +0000
@@ -1,27 +1,30 @@
 583       (*pointer_to_call0a) (c, s, i, l);    /* First step into call0a.  */
    mov    0x804d060,%ebx
    mov    0x804d050,%ecx
    movzwl 0x804d040,%eax
    movswl %ax,%edx
    movzbl 0x804d030,%eax
    movsbl %al,%eax
-   mov    %ebx,0xc(%esp)
-   mov    %ecx,0x8(%esp)
-   mov    %edx,0x4(%esp)
-   mov    %eax,(%esp)
-   mov    0x7c(%esp),%eax
+   push   %ebx
+   push   %ecx
+   push   %edx
+   push   %eax
+   mov    -0x1c(%ebp),%eax
    call   *%eax
+   add    $0x10,%esp

 584	   (*pointer_to_call0a) (c, s, i, l);    /* Second step into call0a.  */
    mov    0x804d060,%ebx
    mov    0x804d050,%ecx
    movzwl 0x804d040,%eax
    movswl %ax,%edx
    movzbl 0x804d030,%eax
    movsbl %al,%eax
-   mov    %ebx,0xc(%esp)
-   mov    %ecx,0x8(%esp)
-   mov    %edx,0x4(%esp)
-   mov    %eax,(%esp)
-   mov    0x7c(%esp),%eax
+   push   %ebx
+   push   %ecx
+   push   %edx
+   push   %eax
+   mov    -0x1c(%ebp),%eax
    call   *%eax
+   add    $0x10,%esp
+

I don't know why -m32 changed to push/add instead of mov while 64-bit hasn't.

This is most likely needed on non-x86 ports as well.

gdb/testsuite/ChangeLog
2016-01-11  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	* gdb.base/funcargs.exp (finish from indirectly called function):
	Reintroduce the case for 'First'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Reapply: List inferiors/threads/pspaces in ascending order
@ 2016-01-12  1:37 sergiodj+buildbot
  2016-01-12  2:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12  1:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b05b120205e697db6291abb95a8cd2be054f99e9 ***

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

Reapply: List inferiors/threads/pspaces in ascending order

[This reapplies a change that was accidentally reverted with c0ecb95f3d.]

Before:
  (gdb) info threads
    Id   Target Id         Frame
    3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30
    2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2 (arg=0x0) at foo.c:60
  * 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join (threadid=140737353893632, thread_return=0x0) at pthread_join.c:92

After:
  (gdb) info threads
    Id   Target Id         Frame
  * 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join (threadid=140737353893632, thread_return=0x0) at pthread_join.c:92
    2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2 (arg=0x0) at foo.c:60
    3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30

gdb/doc/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.texinfo (Inferiors and Programs): Adjust "maint info
	program-spaces" example to ascending order listing.
	(Threads): Adjust "info threads" example to ascending order
	listing.
	(Forks): Adjust "info inferiors" example to ascending order
	listing.

gdb/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* inferior.c (add_inferior_silent): Append the new inferior to the
	end of the list.
	* progspace.c (add_program_space): Append the new pspace to the
	end of the list.
	* thread.c (new_thread): Append the new thread to the end of the
	list.

gdb/testsuite/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.base/foll-exec-mode.exp: Adjust to GDB listing inferiors and
	threads in ascending order.
	* gdb.base/foll-fork.exp: Likewise.
	* gdb.base/foll-vfork.exp: Likewise.
	* gdb.base/multi-forks.exp: Likewise.
	* gdb.mi/mi-nonstop.exp: Likewise.
	* gdb.mi/mi-nsintrall.exp: Likewise.
	* gdb.multi/base.exp: Likewise.
	* gdb.multi/multi-arch.exp: Likewise.
	* gdb.python/py-inferior.exp: Likewise.
	* gdb.threads/break-while-running.exp: Likewise.
	* gdb.threads/execl.exp: Likewise.
	* gdb.threads/gcore-thread.exp: Likewise.
	* gdb.threads/info-threads-cur-sal.exp: Likewise.
	* gdb.threads/kill.exp: Likewise.
	* gdb.threads/linux-dp.exp: Likewise.
	* gdb.threads/multiple-step-overs.exp: Likewise.
	* gdb.threads/next-bp-other-thread.exp: Likewise.
	* gdb.threads/step-bg-decr-pc-switch-thread.exp: Likewise.
	* gdb.threads/step-over-lands-on-breakpoint.exp: Likewise.
	* gdb.threads/step-over-trips-on-watchpoint.exp: Likewise.
	* gdb.threads/thread-find.exp: Likewise.
	* gdb.threads/tls.exp: Likewise.
	* lib/mi-support.exp (mi_reverse_list): Delete.
	(mi_check_thread_states): No longer reverse list.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: mips: workaround 32-bit addr sign extensions
@ 2016-01-12  6:46 sergiodj+buildbot
  2016-01-12  8:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12  6:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b36d953bced0a4fecdde1823abac70ed7038ee95 ***

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

sim: mips: workaround 32-bit addr sign extensions

The mips bfd will sign extend 32-bit addresses into 64-bit values,
so if the entry happens to be 0x80000000 or higher, it is turned to
0xffffffff80000000 which points to memory that doesn't exist.

This wasn't an issue until commit 26f8bf63bf36f9062a5cc1afacf71462a
as all addresses were automatically truncated there in the translate
function to 32-bits.  When we cleaned up that code, the full 64-bits
were checked leading to many test failures for mips-sde-elf targets
and such.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Hurd: Make gdb/reply_mig_hack.awk script compatible to "mawk"
@ 2016-01-12 12:01 sergiodj+buildbot
  2016-01-12 13:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 12:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5eddd57823971bdb54f957d10c11ff3fc9f97b1e ***

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

Hurd: Make gdb/reply_mig_hack.awk script compatible to "mawk"

The "mawk" AWK implementation did't like that regular expression:

    mawk: [...]/gdb/reply_mig_hack.awk: line 98: regular expression compile failed (missing operand)

	gdb/
	* reply_mig_hack.awk: Rewrite one regular expression.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Test gdb.base/random-signal.exp with "attach"
@ 2016-01-12 13:13 sergiodj+buildbot
  2016-01-12 14:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 13:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e46eeeddfb308cacd863f11a433c10ff1d403827 ***

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

Test gdb.base/random-signal.exp with "attach"

This exposes the issued fixed by 2f99e8fc9cb8:

  https://sourceware.org/ml/gdb-patches/2015-12/msg00423.html

to native debugging as well.

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

	* gdb.base/random-signal.exp (do_test): New procedure, with body
	of testcase moved in.
	(top level) Call it twice, once with "run" and once with "attach".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove trademark acknowledgements throughout
@ 2016-01-12 15:09 sergiodj+buildbot
  2016-01-12 17:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc504a311794145e7aef2011f31ea87aa64bea4c ***

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

Remove trademark acknowledgements throughout

The GNU Coding Standards say:

  "Please do not include any trademark acknowledgements in GNU
  software packages or documentation."

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

	Remove use of the registered trademark symbol throughout.

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

	Remove use of the registered trademark symbol throughout.

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

	Remove use of the registered trademark symbol throughout.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Change function signature passed to clone
@ 2016-01-12 15:22 sergiodj+buildbot
  2016-01-12 18:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba4dd7c4a1d99c62a1c2edd68f511a82f8fe041e ***

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

Change function signature passed to clone

I see the following compile error with an old bfin-uclinux gcc to
build GDBserver,

 cc1: warnings being treated as errors
 gdb/gdbserver/../nat/linux-ptrace.c: In function 'linux_fork_to_function':
 gdb/gdbserver/../nat/linux-ptrace.c:283: error: passing argument 1 of 'clone' from incompatible pointer type

in glibc, clone's prototype is like this, and in uClibc, it is the same,

       int clone(int (*fn)(void *), void *child_stack,
                 int flags, void *arg, ...
                 /* pid_t *ptid, struct user_desc *tls, pid_t *ctid */ );

so this patch changes function signature from 'void (*function) (gdb_byte *)'
to 'int (*function) (void *)'.

Note that I find Pedro advised to change argument type from 'void *'
to 'gdb_byte *' during the patch review
https://sourceware.org/ml/gdb-patches/2013-08/msg00611.html  however,
I think fix compile error can justify the change back to 'void *'.

gdb:

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

	* nat/linux-ptrace.c (linux_fork_to_function): Change type
	of argument 'function'.
	(linux_grandchild_function): Change return type to 'int'.
	Change child_stack's type to 'void *'.
	(linux_child_function): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbserver: fix various warnings
@ 2016-01-12 15:44 sergiodj+buildbot
  2016-01-12 20:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b3da067f0893be637f9e992b409e36682ea081a ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5b3da067f0893be637f9e992b409e36682ea081a

gdbserver: fix various warnings

Delete unused funcs, update old prototypes, and mark local funcs
as static.  This doesn't cover all missing prototype warnings.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbserver: use the new gdb warning helpers
@ 2016-01-12 15:45 sergiodj+buildbot
  2016-01-12 21:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f13a3ce8afc1144169a14c7704689e263316e70 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8f13a3ce8afc1144169a14c7704689e263316e70

gdbserver: use the new gdb warning helpers

We need to use -Wno-missing-prototypes for now as much of the code
sticks externs in local files and not in common headers.

2016-01-11  Mike Frysinger  <vapier@gentoo.org>

	* acinclude.m4: Include new ../warning.m4 file.
	* configure: Regenerated.
	* configure.ac: Replace all warning logic with AM_GDB_WARNINGS.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix invalid conversion from void * to gdb_byte *
@ 2016-01-12 16:34 sergiodj+buildbot
  2016-01-12 23:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d18547d8b08615a58db18ad3e43f721dc92ae298 ***

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

Fix invalid conversion from void * to gdb_byte *

This patch fixes the following GDB build error in C++ mode.

gdb/nat/linux-ptrace.c: In function 'int linux_child_function(void*)':
gdb/nat/linux-ptrace.c:323:65: error: invalid conversion from 'void*' to 'gdb_byte* {aka unsigned char*}' [-fpermissive]
   linux_fork_to_function (child_stack, linux_grandchild_function);
                                                                 ^

gdb:

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

	* nat/linux-ptrace.c (linux_child_function): Cast child_stack
	to gdb_byte * and pass to linux_fork_to_function.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Sync top-level Makefile.def with GCC
@ 2016-01-12 16:37 sergiodj+buildbot
  2016-01-13  0:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce5e165eae8925f64da52172f3e67ad8010a1aa0 ***

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

Sync top-level Makefile.def with GCC

2016-01-12  Bernd Edlinger  <bernd.edlinger@hotmail.de>

	PR bootstrap/69134
	* Makefile.def (mpfr): Disable assembler.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add cantunwind when unwind info does not match start of section.
@ 2016-01-12 16:41 sergiodj+buildbot
  2016-01-13  1:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac06903dcff237777c8d507a03aafd79c84129ae ***

Author: Yury Usishchev <y.usishchev@samsung.com>
Branch: master
Commit: ac06903dcff237777c8d507a03aafd79c84129ae

Add cantunwind when unwind info does not match start of section.

bfd     * elf32-arm.c (elf32_arm_fix_exidx_coverage): Insert cantunwind when
        address in first unwind entry does not match start of section.

tests   * ld-arm/arm-elf.exp: New test.
        * ld-arm/unwind-mix.d: New file.
        * ld-arm/unwind-mix1.s: New file.
        * ld-arm/unwind-mix2.s: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] Support ARMv8.2 RAS extension.
@ 2016-01-12 16:46 sergiodj+buildbot
  2016-01-13  3:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 105bde5771c1c1b26b69e3623c88f3caafa3a480 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 105bde5771c1c1b26b69e3623c88f3caafa3a480

[ARM] Support ARMv8.2 RAS extension.

The ARMv8.2 architecture includes the RAS extension which adds an
instruction, ESB, and a number of coprocessor registers. This patch adds
the instruction to binutils, making it available when -march=armv8.2-a
is selected. It also adds tests for the instruction and for the
coprocessor registers.

gas/
2016-01-12  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-arm.c (arm_ext_v8_2): New.
	(insns): Add "esb".
	* testsuite/gas/arm/armv8_2-a.d: New.
	* testsuite/gas/arm/armv8_2-a.s: New.

opcodes/
2016-01-12  Matthew Wahab  <matthew.wahab@arm.com>

	* arm-dis.c (arm_opcodes): Add "esb".
	(thumb_opcodes): Likewise.

Change-Id: I67f3d70789db78d1c66a56c4994675f99ac15e34


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Sync top-level btool.m4 with GCC
@ 2016-01-12 16:49 sergiodj+buildbot
  2016-01-13  4:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1985dc2d048a4134f20dc9cda61255eb33289476 ***

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

Sync top-level btool.m4 with GCC

	Sync with GCC
	2015-11-26  David Edelsohn  <dje.gcc@gmail.com>

	* m4/libtool.m4 (export_symbols_cmds) [AIX]: Add global TLS "L"
	symbols.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Implement 'catch syscall' for gdbserver
@ 2016-01-12 20:34 sergiodj+buildbot
  2016-01-13  5:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 20:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82075af2c14b1f8a54fa5796fb63f7ef23f98d9d ***

Author: Josh Stone <jistone@redhat.com>
Branch: master
Commit: 82075af2c14b1f8a54fa5796fb63f7ef23f98d9d

Implement 'catch syscall' for gdbserver

This adds a new QCatchSyscalls packet to enable 'catch syscall', and new
stop reasons "syscall_entry" and "syscall_return" for those events.  It
is currently only supported on Linux x86 and x86_64.

gdb/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* NEWS (Changes since GDB 7.10): Mention QCatchSyscalls and the
	syscall_entry and syscall_return stop reasons.  Mention GDB
	support for remote catch syscall.
	* remote.c (PACKET_QCatchSyscalls): New enum.
	(remote_set_syscall_catchpoint): New function.
	(remote_protocol_features): New element for QCatchSyscalls.
	(remote_parse_stop_reply): Parse syscall_entry/return stops.
	(init_remote_ops): Install remote_set_syscall_catchpoint.
	(_initialize_remote): Config QCatchSyscalls.
	* linux-nat.h (struct lwp_info) <syscall_state>: Comment typo.

gdb/doc/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.texinfo (Remote Configuration): List the QCatchSyscalls packet.
	(Stop Reply Packets): List the syscall entry and return stop reasons.
	(General Query Packets): Describe QCatchSyscalls, and add it to the
	table and the detailed list of stub features.

gdb/gdbserver/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* inferiors.h: Include "gdb_vecs.h".
	(struct process_info): Add syscalls_to_catch.
	* inferiors.c (remove_process): Free syscalls_to_catch.
	* remote-utils.c (prepare_resume_reply): Report syscall_entry and
	syscall_return stops.
	* server.h (UNKNOWN_SYSCALL, ANY_SYSCALL): Define.
	* server.c (handle_general_set): Handle QCatchSyscalls.
	(handle_query): Report support for QCatchSyscalls.
	* target.h (struct target_ops): Add supports_catch_syscall.
	(target_supports_catch_syscall): New macro.
	* linux-low.h (struct linux_target_ops): Add get_syscall_trapinfo.
	(struct lwp_info): Add syscall_state.
	* linux-low.c (handle_extended_wait): Mark syscall_state as an entry.
	Maintain syscall_state and syscalls_to_catch across exec.
	(get_syscall_trapinfo): New function, proxy to the_low_target.
	(linux_low_ptrace_options): Enable PTRACE_O_TRACESYSGOOD.
	(linux_low_filter_event): Toggle syscall_state entry/return for
	syscall traps, and set it ignored for all others.
	(gdb_catching_syscalls_p): New function.
	(gdb_catch_this_syscall_p): New function.
	(linux_wait_1): Handle SYSCALL_SIGTRAP.
	(linux_resume_one_lwp_throw): Add PTRACE_SYSCALL possibility.
	(linux_supports_catch_syscall): New function.
	(linux_target_ops): Install it.
	* linux-x86-low.c (x86_get_syscall_trapinfo): New function.
	(the_low_target): Install it.

gdb/testsuite/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.base/catch-syscall.c (do_execve): New variable.
	(main): Conditionally trigger an execve.
	* gdb.base/catch-syscall.exp: Enable testing for remote targets.
	(test_catch_syscall_execve): New, check entry/return across execve.
	(do_syscall_tests): Call test_catch_syscall_execve.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR19388: Can't access $_siginfo in breakpoint (catch signal) condition
@ 2016-01-13 10:52 sergiodj+buildbot
  2016-01-13 12:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 10:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a911d87ad714cbfbbc5c5752cb8b445a7e70196c ***

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

Fix PR19388: Can't access $_siginfo in breakpoint (catch signal) condition

This commit merges both the registers and $_siginfo "thread
running/executing" checks into a single function.

Accessing $_siginfo from a "catch signal" breakpoint condition doesn't
work.  The condition always fails with "Selected thread is running":

 (gdb) catch signal
 Catchpoint 3 (standard signals)
 (gdb)
 condition $bpnum $_siginfo.si_signo == 5
 (gdb) continue
 Continuing.
 Error in testing breakpoint condition:
 Selected thread is running.

 Catchpoint 3 (signal SIGUSR1), 0x0000003615e35877 in __GI_raise (sig=10) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
 56        return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
 (gdb)

When accessing the $_siginfo object, we check whether the thread is
marked running (external/public) state and refuse the access if so.
This is so "print $_siginfo" at the prompt fails nicelly when the
current thread is running.  While evaluating breakpoint conditionals,
we haven't decided yet whether the thread is going to stop, so
is_running still returns true, and we thus always error out.

Evaluating an expression that requires registers access is really
conceptually the same -- we could think of $_siginfo as a pseudo
register.  However, in that case we check whether the thread is marked
executing (internal/private state), not running (external/public
state).  Changing the $_siginfo validation to check is_executing as
well fixes the bug in question.

Note that checking is_executing is not fully correct, not even for
registers.  See PR 19389.  However, I think this is the lesser of two
evils and ends up as an improvement.  We at least now have a single
place to fix.

Tested on x86_64 GNU/Linux.

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

	PR breakpoints/19388
	* frame.c (get_current_frame): Use validate_registers_access.
	* gdbthread.h (validate_registers_access): Declare.
	* infrun.c (validate_siginfo_access): Delete.
	(siginfo_value_read, siginfo_value_write): Use
	validate_registers_access.
	* thread.c (validate_registers_access): New function.

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

	PR breakpoints/19388
	* gdb.base/catch-signal-siginfo-cond.c: New file.
	* gdb.base/catch-signal-siginfo-cond.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add a new $_inferior convenience variable
@ 2016-01-13 11:35 sergiodj+buildbot
  2016-01-13 13:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3940304fe75c91f99e260a89fe8c45ece7e373f ***

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

Add a new $_inferior convenience variable

Like $_thread, but holds the current inferior number.

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

	* NEWS: Mention $_inferior.
	* inferior.c (inferior_id_make_value): New.
	(inferior_funcs): New.
	(_initialize_inferior): Create $_inferior variable.

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

	* gdb.base/default.exp: Expect $_inferior as well.
	* gdb.multi/base.exp: Test $_inferior.

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

	* gdb.texinfo (Inferiors and Programs): Document the $_inferior
	convenience variable.
	(Convenience Vars): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add Python InferiorThread.inferior attribute
@ 2016-01-13 11:36 sergiodj+buildbot
  2016-01-13 15:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8465445732dc04c3fb6cf954274e12d06b274f08 ***

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

Add Python InferiorThread.inferior attribute

So a script can easily get at a thread's inferior and its number.

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

	* NEWS: Mention InferiorThread.inferior.
	* python/py-infthread.c (thpy_get_inferior): New.
	(thread_object_getset): Register "inferior".

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

	* gdb.python/py-infthread.exp: Test InferiorThread.inferior.

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

	* python.texi (Threads In Python): Document
	InferiorThread.inferior.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Centralize thread ID printing
@ 2016-01-13 11:38 sergiodj+buildbot
  2016-01-13 16:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43792cf0de3a49fb871d432343672bdf16270e99 ***

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

Centralize thread ID printing

Add a new function to print a thread ID, in the style of paddress,
plongest, etc. and adjust all CLI-reachable paths to use it.

This gives us a single place to tweak to print inferior-qualified
thread IDs later:

 - [Switching to thread 1 (Thread 0x7ffff7fc2740 (LWP 8155))]
 + [Switching to thread 1.1 (Thread 0x7ffff7fc2740 (LWP 8155))]

etc., though for now, this has no user-visible change.

No regressions on x86_64 Fedora 20.

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

	* breakpoint.c (remove_threaded_breakpoints)
	(print_one_breakpoint_location): Use print_thread_id.
	* btrace.c (btrace_enable, btrace_disable, btrace_teardown)
	(btrace_fetch, btrace_clear): Use print_thread_id.
	* common/print-utils.c (CELLSIZE): Delete.
	(get_cell): Rename to ...
	(get_print_cell): ... this and made extern.  Adjust call callers.
	Adjust to use PRINT_CELL_SIZE.
	* common/print-utils.h (get_print_cell): Declare.
	(PRINT_CELL_SIZE): New.
	* gdbthread.h (print_thread_id): Declare.
	* infcmd.c (signal_command): Use print_thread_id.
	* inferior.c (print_inferior): Use print_thread_id.
	* infrun.c (handle_signal_stop)
	(insert_exception_resume_breakpoint)
	(insert_exception_resume_from_probe)
	(print_signal_received_reason): Use print_thread_id.
	* record-btrace.c (record_btrace_info)
	(record_btrace_resume_thread, record_btrace_cancel_resume)
	(record_btrace_step_thread, record_btrace_wait): Use
	print_thread_id.
	* thread.c (thread_apply_all_command): Use print_thread_id.
	(print_thread_id): New function.
	(thread_apply_command): Use print_thread_id.
	(thread_command, thread_find_command, do_captured_thread_select):
	Use print_thread_id.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Per-inferior/Inferior-qualified thread IDs
@ 2016-01-13 11:39 sergiodj+buildbot
  2016-01-13 17:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d5658a1d3c3eb2a09c03f2f0662a1c01963c869 ***

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

Per-inferior/Inferior-qualified thread IDs

This commit changes GDB to track thread numbers per-inferior.  Then,
if you're debugging multiple inferiors, GDB displays
"inferior-num.thread-num" instead of just "thread-num" whenever it
needs to display a thread:

 (gdb) info inferiors
   Num  Description       Executable
   1    process 6022     /home/pedro/gdb/tests/threads
 * 2    process 6037     /home/pedro/gdb/tests/threads
 (gdb) info threads
   Id   Target Id         Frame
   1.1  Thread 0x7ffff7fc2740 (LWP 6022) "threads" (running)
   1.2  Thread 0x7ffff77c0700 (LWP 6028) "threads" (running)
   1.3  Thread 0x7ffff7fc2740 (LWP 6032) "threads" (running)
   2.1  Thread 0x7ffff7fc1700 (LWP 6037) "threads" (running)
   2.2  Thread 0x7ffff77c0700 (LWP 6038) "threads" (running)
 * 2.3  Thread 0x7ffff7fc2740 (LWP 6039) "threads" (running)
 (gdb)
...
 (gdb) thread 1.1
 [Switching to thread 1.1 (Thread 0x7ffff7fc2740 (LWP 8155))]
 (gdb)
...

etc.

You can still use "thread NUM", in which case GDB infers you're
referring to thread NUM of the current inferior.

The $_thread convenience var and Python's InferiorThread.num attribute
are remapped to the new per-inferior thread number.  It's a backward
compatibility break, but since it only matters when debugging multiple
inferiors, I think it's worth doing.

Because MI thread IDs need to be a single integer, we keep giving
threads a global identifier, _in addition_ to the per-inferior number,
and make MI always refer to the global thread IDs.  IOW, nothing
changes from a MI frontend's perspective.

Similarly, since Python's Breakpoint.thread and Guile's
breakpoint-thread/set-breakpoint-thread breakpoint methods need to
work with integers, those are adjusted to work with global thread IDs
too.  Follow up patches will provide convenient means to access
threads' global IDs.

To avoid potencially confusing users (which also avoids updating much
of the testsuite), if there's only one inferior and its ID is "1",
IOW, the user hasn't done anything multi-process/inferior related,
then the "INF." part of thread IDs is not shown.  E.g,.:

 (gdb) info inferiors
   Num  Description       Executable
 * 1    process 15275     /home/pedro/gdb/tests/threads
 (gdb) info threads
   Id   Target Id         Frame
 * 1    Thread 0x7ffff7fc1740 (LWP 15275) "threads" main () at threads.c:40
 (gdb) add-inferior
 Added inferior 2
 (gdb) info threads
   Id   Target Id         Frame
 * 1.1  Thread 0x7ffff7fc1740 (LWP 15275) "threads" main () at threads.c:40
 (gdb)

No regressions on x86_64 Fedora 20.

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

	* NEWS: Mention that thread IDs are now per inferior and global
	thread IDs.
	* Makefile.in (SFILES): Add tid-parse.c.
	(COMMON_OBS): Add tid-parse.o.
	(HFILES_NO_SRCDIR): Add tid-parse.h.
	* ada-tasks.c: Adjust to use ptid_to_global_thread_id.
	* breakpoint.c (insert_breakpoint_locations)
	(remove_threaded_breakpoints, bpstat_check_breakpoint_conditions)
	(print_one_breakpoint_location, set_longjmp_breakpoint)
	(check_longjmp_breakpoint_for_call_dummy)
	(set_momentary_breakpoint): Adjust to use global IDs.
	(find_condition_and_thread, watch_command_1): Use parse_thread_id.
	(until_break_command, longjmp_bkpt_dtor)
	(breakpoint_re_set_thread, insert_single_step_breakpoint): Adjust
	to use global IDs.
	* dummy-frame.c (pop_dummy_frame_bpt): Adjust to use
	ptid_to_global_thread_id.
	* elfread.c (elf_gnu_ifunc_resolver_stop): Likewise.
	* gdbthread.h (struct thread_info): Rename field 'num' to
	'global_num.  Add new fields 'per_inf_num' and 'inf'.
	(thread_id_to_pid): Rename thread_id_to_pid to
	global_thread_id_to_ptid.
	(pid_to_thread_id): Rename to ...
	(ptid_to_global_thread_id): ... this.
	(valid_thread_id): Rename to ...
	(valid_global_thread_id): ... this.
	(find_thread_id): Rename to ...
	(find_thread_global_id): ... this.
	(ALL_THREADS, ALL_THREADS_BY_INFERIOR): Declare.
	(print_thread_info): Add comment.
	* tid-parse.h: New file.
	* tid-parse.c: New file.
	* infcmd.c (step_command_fsm_prepare)
	(step_command_fsm_should_stop): Adjust to use the global thread
	ID.
	(until_next_command, until_next_command)
	(finish_command_fsm_should_stop): Adjust to use the global thread
	ID.
	(attach_post_wait): Adjust to check the inferior number too.
	* inferior.h (struct inferior) <highest_thread_num>: New field.
	* infrun.c (handle_signal_stop)
	(insert_exception_resume_breakpoint)
	(insert_exception_resume_from_probe): Adjust to use the global
	thread ID.
	* record-btrace.c (record_btrace_open): Use global thread IDs.
	* remote.c (process_initial_stop_replies): Also consider the
	inferior number.
	* target.c (target_pre_inferior): Clear the inferior's highest
	thread num.
	* thread.c (clear_thread_inferior_resources): Adjust to use the
	global thread ID.
	(new_thread): New inferior parameter.  Adjust to use it.  Set both
	the thread's global ID and the thread's per-inferior ID.
	(add_thread_silent): Adjust.
	(find_thread_global_id): New.
	(find_thread_id): Make static.  Adjust to rename.
	(valid_thread_id): Rename to ...
	(valid_global_thread_id): ... this.
	(pid_to_thread_id): Rename to ...
	(ptid_to_global_thread_id): ... this.
	(thread_id_to_pid): Rename to ...
	(global_thread_id_to_ptid): ... this.  Adjust.
	(first_thread_of_process): Adjust.
	(do_captured_list_thread_ids): Adjust to use global thread IDs.
	(should_print_thread): New function.
	(print_thread_info): Rename to ...
	(print_thread_info_1): ... this, and add new show_global_ids
	parameter.  Handle it.  Iterate over inferiors.
	(print_thread_info): Reimplement as wrapper around
	print_thread_info_1.
	(show_inferior_qualified_tids): New function.
	(print_thread_id): Use it.
	(tp_array_compar): Compare inferior numbers too.
	(thread_apply_command): Use tid_range_parser.
	(do_captured_thread_select): Use parse_thread_id.
	(thread_id_make_value): Adjust.
	(_initialize_thread): Adjust "info threads" help string.
	* varobj.c (struct varobj_root): Update comment.
	(varobj_create): Adjust to use global thread IDs.
	(value_of_root_1): Adjust to use global_thread_id_to_ptid.
	* windows-tdep.c (display_tib): No longer accept an argument.
	* cli/cli-utils.c (get_number_trailer): Make extern.
	* cli/cli-utils.h (get_number_trailer): Declare.
	(get_number_const): Adjust documentation.
	* mi/mi-cmd-var.c (mi_cmd_var_update_iter): Adjust to use global
	thread IDs.
	* mi/mi-interp.c (mi_new_thread, mi_thread_exit)
	(mi_on_normal_stop, mi_output_running_pid, mi_on_resume):
	* mi/mi-main.c (mi_execute_command, mi_cmd_execute): Likewise.
	* guile/scm-breakpoint.c (gdbscm_set_breakpoint_thread_x):
	Likewise.
	* python/py-breakpoint.c (bppy_set_thread): Likewise.
	* python/py-finishbreakpoint.c (bpfinishpy_init): Likewise.
	* python/py-infthread.c (thpy_get_num): Add comment and return the
	per-inferior thread ID.
	(thread_object_getset): Update comment of "num".

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

	* gdb.base/break.exp: Adjust to output changes.
	* gdb.base/hbreak2.exp: Likewise.
	* gdb.base/sepdebug.exp: Likewise.
	* gdb.base/watch_thread_num.exp: Likewise.
	* gdb.linespec/keywords.exp: Likewise.
	* gdb.multi/info-threads.exp: Likewise.
	* gdb.threads/thread-find.exp: Likewise.
	* gdb.multi/tids.c: New file.
	* gdb.multi/tids.exp: New file.

gdb/doc/ChangeLog:
2016-01-07  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Threads): Document per-inferior thread IDs,
	qualified thread IDs, global thread IDs and thread ID lists.
	(Set Watchpoints, Thread-Specific Breakpoints): Adjust to refer to
	thread IDs.
	(Convenience Vars): Document the $_thread convenience variable.
	(Ada Tasks): Adjust to refer to thread IDs.
	(GDB/MI Async Records, GDB/MI Thread Commands, GDB/MI Ada Tasking
	Commands, GDB/MI Variable Objects): Update to mention global
	thread IDs.
	* guile.texi (Breakpoints In Guile)
	<breakpoint-thread/set-breakpoint-thread breakpoint>: Mention
	global thread IDs instead of thread IDs.
	* python.texi (Threads In Python): Adjust documentation of
	InferiorThread.num.
	(Breakpoint.thread): Mention global thread IDs instead of thread
	IDs.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add Python InferiorThread.global_num attribute
@ 2016-01-13 11:40 sergiodj+buildbot
  2016-01-13 19:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22a0232400ea09c57ab70d97cffc1f25e6320da7 ***

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

Add Python InferiorThread.global_num attribute

This commit adds a new Python InferiorThread.global_num attribute.
This can be used to pass the correct thread ID to Breakpoint.thread,
which takes a global thread ID, not a per-inferior thread number.

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

	* NEWS: Mention InferiorThread.global_num.
	* python/py-infthread.c (thpy_get_global_num): New function.
	(thread_object_getset): Register "global_num".

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

	* gdb.multi/tids.exp: Test InferiorThread.global_num and
	Breakpoint.thread.
	* gdb.python/py-infthread.exp: Test InferiorThread.global_num.

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

	* python.texi (Breakpoints In Python) <Breakpoint.thread>: Add
	anchor.
	(Threads In Python): Document new InferiorThread.global_num
	attribute.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Implement "info threads -gid"
@ 2016-01-13 11:41 sergiodj+buildbot
  2016-01-13 20:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c84f6bbfe50ff13928360d3cc349d7c553867ce6 ***

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

Implement "info threads -gid"

This commit makes global thread IDs optionaly visible in "info
threads", with the new "-gid" switch:

 (gdb) info threads -gid
   Id   GId  Target Id         Frame
   1.1  1    Thread 0x7ffff7fc2740 (LWP 6022) "threads" (running)
   1.2  3    Thread 0x7ffff77c0700 (LWP 6028) "threads" (running)
   1.3  4    Thread 0x7ffff7fc2740 (LWP 6032) "threads" (running)
   2.1  2    Thread 0x7ffff7fc1700 (LWP 6037) "threads" (running)
   2.2  5    Thread 0x7ffff77c0700 (LWP 6038) "threads" (running)
 * 2.3  6    Thread 0x7ffff7fc2740 (LWP 6039) "threads" (running)

 (gdb) info threads
   Id   Target Id         Frame
   1.1  Thread 0x7ffff7fc2740 (LWP 6022) "threads" (running)
   1.2  Thread 0x7ffff77c0700 (LWP 6028) "threads" (running)
   1.3  Thread 0x7ffff7fc2740 (LWP 6032) "threads" (running)
   2.1  Thread 0x7ffff7fc1700 (LWP 6037) "threads" (running)
   2.2  Thread 0x7ffff77c0700 (LWP 6038) "threads" (running)
 * 2.3  Thread 0x7ffff7fc2740 (LWP 6039) "threads" (running)

No regressions on x86_64 Fedora 20.

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

	* NEWS: Mention "info threads -gid".
	* gdbthread.h (struct thread_info) <global_num>: Mention "info
	threads -gid".
	* thread.c (info_threads_command): Handle "-gid".
	(_initialize_thread): Adjust "info threads" help string to mention
	-gid.

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

	* gdb.multi/tids.exp: Test "info threads -gid".

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

	* gdb.texinfo (Threads): Document "info threads -gid".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add $_gthread convenience variable
@ 2016-01-13 11:42 sergiodj+buildbot
  2016-01-13 21:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 663f6d42f47265d2deaa86c8a976e658fb13f820 ***

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

Add $_gthread convenience variable

This commit adds a new $_gthread convenience variable, that is like
$_thread, but holds the current thread's global thread id.

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

	* NEWS: Mention $_gthread.
	* gdbthread.h (struct thread_info) <global_num>: Mention
	$_gthread.
	* thread.c (thread_num_make_value_helper): New function.
	(thread_id_make_value): Delete.
	(thread_id_per_inf_num_make_value, global_thread_id_make_value):
	New.
	(thread_funcs): Adjust.
	(gthread_funcs): New.
	(_initialize_thread): Register $_gthread variable.

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

	* gdb.base/default.exp: Expect $_gthread as well.
	* gdb.multi/tids.exp: Test $_gthread.
	* gdb.threads/thread-specific.exp: Test $_gthread.

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

	* gdb.texinfo (Threads): Document the $_gthread convenience
	variable.
	(Convenience Vars): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Read instruction with byte_order_for_code
@ 2016-01-13 16:19 sergiodj+buildbot
  2016-01-13 23:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e7b8beaa3b7b9ac8577b10afa9d58bb9d453b08 ***

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

Read instruction with byte_order_for_code

When reading instruction, we should use byte_order_for_code instead
of byte_order.

gdb:

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

	* arch/arm-get-next-pcs.c (arm_get_next_pcs_raw): Use
	byte_order_for_code to read instruction.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MAINTAINERS: Add Andreas Arnez as s390 target maintainer.
@ 2016-01-13 18:04 sergiodj+buildbot
  2016-01-14  0:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 18:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc06e0b148dfc4f2e52003a17d48463150f72e7b ***

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

MAINTAINERS: Add Andreas Arnez as s390 target maintainer.

gdb/ChangeLog:

	* MAINTAINERS: Add Andreas Arnez as s390 target maintainer.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] Make thumb2_breakpoint static again
@ 2016-01-14  9:39 sergiodj+buildbot
  2016-01-14 11:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-14  9:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b451dda5f8905b26bafafe00423335d4fffe8dd ***

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

[ARM] Make thumb2_breakpoint static again

This patch makes thumb2_breakpoint static.  When writing this patch,
I find the only reason we keep thumb2_breakpoint extern is that it
is used as an argument passed to arm_gdbserver_get_next_pcs.  However,
field arm_thumb2_breakpoint is only used in a null check in
thumb_get_next_pcs_raw, so I wonder why do need to pass thumb2_breakpoint
to arm_gdbserver_get_next_pcs.

thumb2_breakpoint was added by Daniel Jacobowitz in order to support
single-step IT block
https://sourceware.org/ml/gdb-patches/2010-01/msg00624.html  the logic
there was if we have 32-bit thumb-2 breakpoint defined, we can safely
single-step IT block, otherwise, we can't.  Daniel didn't want to use
16-bit thumb BKPT instruction, because it triggers even on instruction
which should be executed.  Secondly, using 16-bit thumb illegal
instruction on top of 32-bit thumb instruction may break the meaning of
original IT blocks, because the other 16-bit can be regarded as an
instruction.  See more explanations from Daniel's kernel patch
http://www.spinics.net/lists/arm-kernel/msg80476.html

Let us back to this patch, GDB/GDBserver can safely single step
IT block if thumb2_breakpoint is defined, but the single step logic
doesn't have to know the thumb-2 breakpoint instruction.  Only
breakpoint insertion mechanism decides to use which breakpoint
instruction.  In the software single step code, instead of pass
thumb2_breakpoint, we can pass a boolean variable
has_thumb2_breakpoint indicate whether the target has thumb-2
breakpoint defined, which is equivalent to the original code.

Regression tested on arm-linux.  No regression.

gdb:

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

	* arch/arm-get-next-pcs.c (arm_get_next_pcs_ctor): Change
	argument arm_thumb2_breakpoint to has_thumb2_breakpoint.
	(thumb_get_next_pcs_raw): Check has_thumb2_breakpoint
	instead.
	* arch/arm-get-next-pcs.h (struct arm_get_next_pcs)
	<arm_thumb2_breakpoint>: Remove.
	<has_thumb2_breakpoint>: New field.
	(arm_get_next_pcs_ctor): Update declaration.
	* arm-linux-tdep.c (arm_linux_software_single_step): Pass
	1 to arm_get_next_pcs_ctor.
	* arm-tdep.c (arm_software_single_step): Pass 0 to
	arm_get_next_pcs_ctor.

gdb/gdbserver:

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

	* linux-aarch32-low.c (thumb2_breakpoint): Make it static.
	* linux-aarch32-low.h (thumb2_breakpoint): Remove declaration.
	* linux-arm-low.c (arm_gdbserver_get_next_pcs): Pass 1 to
	arm_get_next_pcs_ctor.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Fix missing architecture checks for ARMv8.2 system registers.
@ 2016-01-14 11:03 sergiodj+buildbot
  2016-01-14 12:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-14 11:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 651657fa61aa0a2946d56063295a7ce8d73f803b ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 651657fa61aa0a2946d56063295a7ce8d73f803b

[AArch64] Fix missing architecture checks for ARMv8.2 system registers.

Some of the RAS system registers added to binutils as part of the ARMv8.2
support are missing the feature checks to warn when they aren't
supported by the target.

This patch adds the missing feature checks with a test to check that
the correct warnings are given for all the ARMv8.2 system registers.

gas/
2016-01-14  Matthew Wahab  <matthew.wahab@arm.com>

	* testsuite/gas/aarch64/illegal-sysreg-2.l: New.
	* testsuite/gas/aarch64/illegal-sysreg-2.d: New.

opcodes/
2016-01-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_reg_supported_p): Merge conditionals
	testing for RAS support.  Add checks for erxfr_el1, erxctlr_el1,
	erxtatus_el1 and erxaddr_el1.

Change-Id: I66b590ea49c1eb6b0e5c93e0dc2bc9c4e79a52fe


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix C++ build error by casting void *
@ 2016-01-14 12:30 sergiodj+buildbot
  2016-01-14 13:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-14 12:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0518081f09298c67d1e74e0cc592fde8e0c6571 ***

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

Fix C++ build error by casting void *

Two recent patches breaks GDB C++ mode build,

  https://sourceware.org/ml/gdb-patches/2016-01/msg00150.html
  https://sourceware.org/ml/gdb-patches/2016-01/msg00086.html

gdb/remote.c: In function 'int remote_set_syscall_catchpoint(target_ops*, int, int, int, int, int*)':
gdb/remote.c:2036:39: error: invalid conversion from 'void*' to 'char*' [-fpermissive]
       catch_packet = xmalloc (maxpktsz);
                                       ^

gdb/thread.c: In function 'int do_captured_thread_select(ui_out*, void*)':
gdb/git/gdb/thread.c:1999:24: error: invalid conversion from 'void*' to 'const char*' [-fpermissive]
   const char *tidstr = tidstr_v;
                        ^

this patch fixes them by casting void * to the right type.

gdb:

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

	* remote.c (remote_set_syscall_catchpoint): Cast to char *.
	* thread.c (do_captured_thread_select): Cast to const char *.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] Remove field syscall_next_pc in struct gdbarch_tdep
@ 2016-01-14 14:57 sergiodj+buildbot
  2016-01-14 16:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-14 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7cf25a8ab54cd02b48e7443ef25764475f02315 ***

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

[ARM] Remove field syscall_next_pc in struct gdbarch_tdep

Field syscall_next_pc in struct gdbarch_tdep was to calculate the
next pc of syscall instruction.  On linux target, syscall_next_pc
is set to arm_linux_syscall_next_pc, to do linux specific things.
However, after we have struct arm_get_next_pcs_ops, we can do the
same thing in struct arm_get_next_pcs_ops field syscall_next_pc,
so syscall_next_pc in struct gdbarch_tdep is not needed any more.

gdb:

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

	* arm-linux-tdep.c (arm_linux_get_next_pcs_syscall_next_pc):
	Declare.
	(arm_linux_get_next_pcs_ops): Install
	arm_linux_get_next_pcs_syscall_next_pc.
	(arm_linux_syscall_next_pc): Change to ...
	(arm_linux_get_next_pcs_syscall_next_pc): ... it.
	(arm_linux_init_abi): Don't set tdep->syscall_next_pc.
	* arm-tdep.c (arm_get_next_pcs_syscall_next_pc): Declare.
	(arm_get_next_pcs_syscall_next_pc): Make it static.  Don't
	call tdep->syscall_next_pc.
	* arm-tdep.h (struct gdbarch_tdep) <syscall_next_pc>: Remove.
	(arm_get_next_pcs_syscall_next_pc): Remove.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix display of RL78 MOVW instructions that use the stack pointer.
@ 2016-01-14 16:27 sergiodj+buildbot
  2016-01-14 17:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-14 16:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d82fe66e8d38b20ad429cb99a99ed8741336d72 ***

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

Fix display of RL78 MOVW instructions that use the stack pointer.

	* rl78-decode.opc (rl78_decode_opcode): Add 's' operand to movw
	instructions that can support stack pointer operations.
	* rl78-decode.c: Regenerate.
	* rl78-dis.c: Fix display of stack pointer in MOVW based
	instructions.

	* testsuite/gas/rl78/sp-relative-movw.s: New test.
	* testsuite/gas/rl78/sp-relative-movw.d: Expected disassembly.
	* testsuite/gas/rl78/rl78.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix "thread apply $conv_var" and misc other related problems
@ 2016-01-15 21:59 sergiodj+buildbot
  2016-01-15 23:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-15 21:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f5b7598805c8253c43c989a540a2408c8b685ad ***

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

Fix "thread apply $conv_var" and misc other related problems

This fixes a few bugs in "thread apply".

While this works:

 (gdb) thread apply 1 p 1234

 Thread 1 (Thread 0x7ffff7fc1740 (LWP 14048)):
 $1 = 1234

This doesn't:

 (gdb) thread apply $thr p 1234

 Thread 1 (Thread 0x7ffff7fc1740 (LWP 12039)):
 Invalid thread ID: p 1234
 (gdb)

~~~~

Also, while this works:
 (gdb) thread apply 1
 Please specify a command following the thread ID list

This doesn't:
 (gdb) thread apply $thr
 Thread 1 (Thread 0x7ffff7fc1740 (LWP 12039)):
 [Current thread is 1 (Thread 0x7ffff7fc1740 (LWP 12039))]
 (gdb)

~~~~

And, while this works:
 (gdb) thread apply
 Please specify a thread ID list

This obviously bogus invocation is just silent:
 (gdb) thread apply bt
 (gdb)

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

	* thread.c (thread_apply_command): Use the tid range parser to
	advance past the thread ID list.
	* tid-parse.c (get_positive_number_trailer): New function.
	(parse_thread_id): Use it.
	(get_tid_or_range): Use it.  Return 0 instead of throwing invalid
	thread ID error.
	(get_tid_or_range): Detect negative values.  Return 0 instead of
	throwing invalid thread ID error.

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

	* gdb.multi/tids.exp (thr_apply_info_thr_error): Remove "p 1234"
	command from "thread apply" invocation.
	(thr_apply_info_thr_invalid): Default the expected output to the
	input tid list.
	(top level): Add tests that use convenience variables.  Add tests
	for "thread apply" with a valid TID list, but missing the command.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Star wildcard ranges (e.g., "info thread 2.*")
@ 2016-01-15 22:25 sergiodj+buildbot
  2016-01-16  0:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-15 22:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71ef29a86b252a4780517fc9b2bf9f7d3dd2d991 ***

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

Star wildcard ranges (e.g., "info thread 2.*")

Add support for specifying "all threads of inferior N", by writing "*"
as thread number/range in thread ID lists.

E.g., "info threads 2.*" or "thread apply 2.* bt".

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

	* NEWS: Mention star wildcard ranges.
	* cli/cli-utils.c (get_number_or_range): Check state->in_range first.
	(number_range_setup_range): New function.
	* cli/cli-utils.h (number_range_setup_range): New declaration.
	* thread.c (thread_apply_command): Support star TID ranges.
	* tid-parse.c (tid_range_parser_finished)
	(tid_range_parser_string, tid_range_parser_skip)
	(get_tid_or_range, get_tid_or_range): Handle
	TID_RANGE_STATE_STAR_RANGE.
	(tid_range_parser_star_range): New function.
	* tid-parse.h (enum tid_range_state) <TID_RANGE_STATE_STAR_RANGE>:
	New value.
	(tid_range_parser_star_range): New declaration.

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

	* gdb.texinfo (Threads) <thread ID lists>: Document star ranges.

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

	* gdb.multi/tids.exp: Test star wildcard ranges.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix phony_iconv wide character support.
@ 2016-01-15 22:55 sergiodj+buildbot
  2016-01-16  1:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-15 22:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f74f61cbf72dc158832d81d6ecd6f970f93798cc ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: f74f61cbf72dc158832d81d6ecd6f970f93798cc

Fix phony_iconv wide character support.

2016-01-15  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* charset.c [PHONY_ICONV] (GDB_DEFAULT_HOST_CHARSET):
	Conditionalize for Windows host.
	(GDB_DEFAULT_TARGET_CHARSET): Match GDB_DEFAULT_HOST_CHARSET.
	(GDB_DEFAULT_TARGET_WIDE_CHARSET): Use UTF-32.
	(phony_iconv_open): Handle both UTF-32 endiannesses.
	(phony_iconv): Likewise.  Check for output overflow and clean up
	out-of-input cases.  Correct adjustment to input buffer pointer.
	(set_be_le_names) [PHONY_ICONV]: Use hard-wired names to match
	phony_iconv_open.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Regen configure
@ 2016-01-17  3:05 sergiodj+buildbot
  2016-01-17  4:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  3:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c14705fb3dfb359235314f22392e7a5ce6d4085 ***

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

Regen configure

Picks up 2016-01-12 libtool.m4 change.

bfd/
	* configure: Regenerate.
binutils/
	* configure: Regenerate.
gas/
	* configure: Regenerate.
gprof/
	* configure: Regenerate.
ld/
	* configure: Regenerate.
opcodes/
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] minor reformatting in sim/common/sim-fpu.c.
@ 2016-01-17  5:43 sergiodj+buildbot
  2016-01-17  6:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  5:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c8e93b7fab5b9d8ddb786772ab00d65ec127159 ***

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

minor reformatting in sim/common/sim-fpu.c.

This patch just makes a copy of formatting changes to better conform
with the GNU Coding Style.

sim/common/ChangeLog:

        * sim-fpu.c (print_bits): Minor reformatting (no code change).
        (sim_fpu_map): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Minor comment fixes in sim/common/sim-fpu.c.
@ 2016-01-17  6:14 sergiodj+buildbot
  2016-01-17  8:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  6:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f749ed6079486300a65d7407e9fa3a7a296827f6 ***

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

Minor comment fixes in sim/common/sim-fpu.c.

This patch makes a fair number of fixes in the various comments of
sim-fpu.c, mostly to either better conform to the GNU Coding Standards
(sentences start with a capital letter, end with a period), or to
fix spelling mistakes.

sim/common/ChangeLog:

        * sim-fpu.c: Minor comment fixes throughout.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] fix gdb version parsing in src-release.sh
@ 2016-01-17  6:17 sergiodj+buildbot
  2016-01-17  9:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  6:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b677098d4e086c093554a064076e021fec0399e8 ***

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

fix gdb version parsing in src-release.sh

Small change required after we switched the gdb version scheme to
using a -git suffix rather than a -cvs one.

ChangeLog:

        * src-release.sh: Compute the gdb tarball name by stripping
        '-git' rather than '-cvs'.

Tested by running "src-release.sh gdb" and verifying the tarball
name as well as its contents.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] GDB SIGSEGV opening a Fortran program compiled with ifort
@ 2016-01-17  7:04 sergiodj+buildbot
  2016-01-17 10:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  7:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dc365182240722969f044918ecd3cab00da55502 ***

Author: Jonas Hahnfeld <Hahnfeld@itc.rwth-aachen.de>
Branch: master
Commit: dc365182240722969f044918ecd3cab00da55502

GDB SIGSEGV opening a Fortran program compiled with ifort

This patch fixes a SIGSEGV when trying to open a Fortran program
compiled with ifort (reproduced using version using version 16.0.1.150).
The error can be reproduce with most, if not any program. For instance,
a single file only containing "end", compiled with no additional flag,
suffices.

gdb/ChangeLog:

       PR gdb/19208
       * dwarf2read.c (read_partial_die): Do not call set_objfile_main_name
       if the function has no name.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdbserver build failure on targets without fork
@ 2016-01-18 11:57 sergiodj+buildbot
  2016-01-18 13:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 11:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb0edac83f82516bbbd5a0412bbdf7fd27c687f2 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: eb0edac83f82516bbbd5a0412bbdf7fd27c687f2

Fix gdbserver build failure on targets without fork

This commit fixes nat/linux-namespaces.c to build correctly on
targets without fork.

gdb/ChangeLog:

	* nat/linux-namespaces.c (do_fork): New function.
	(linux_mntns_get_helper): Use the above.

gdb/gdbserver/ChangeLog:

	* configure.ac (AC_FUNC_FORK): New check.
	* config.in: Regenerate.
	* configure: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Provide AC_PROG_LEX that copes with LEX=missing from top-level
@ 2016-01-18 12:05 sergiodj+buildbot
  2016-01-18 14:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d961d0d3a797b4d463024a11131e96c213dee27 ***

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

Provide AC_PROG_LEX that copes with LEX=missing from top-level

config/
	PR binutils/19481
	* override.m4 (AC_PROG_LEX): Define.
binutils/
	* configure: Regenerate.
gas/
	* configure: Regenerate.
ld/
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [testsuite] @progbits -> %progbits
@ 2016-01-18 14:40 sergiodj+buildbot
  2016-01-18 15:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 14:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b27896961a641e92a642b352627208233dfeb7f1 ***

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

[testsuite] @progbits -> %progbits

The ARM assembler has "@" as a comment character, so there are compile
errors in {py,scm}-section-script.c,

 gdb compile failed, /tmp/ccHEzYqy.s: Assembler messages:
 /tmp/ccHEzYqy.s:19: Error: junk at end of line, first unrecognized character is `,'
 /tmp/ccHEzYqy.s:24: Error: junk at end of line, first unrecognized character is `,'
 /tmp/ccHEzYqy.s:29: Error: junk at end of line, first unrecognized character is `,'
 /tmp/ccHEzYqy.s:41: Error: junk at end of line, first unrecognized character is `,'

This patch replaces @progbits with %progbits.

gdb/testsuite:

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

	* gdb.guile/scm-section-script.c: Replace @progbits with
	%progbits.
	* gdb.python/py-section-script.c: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_32bit
@ 2016-01-18 15:11 sergiodj+buildbot
  2016-01-18 17:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 15:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 276d4552dfc2dc3906fa2bd8690ea85b3d8ec055 ***

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

Replace some $ARCH_{get,set}_pc with linux_{get,set}_pc_32bit

This patch adds a pair of new functions linux_get_pc_32bit and
linux_set_pc_32bit which get and set 32-bit register "pc" from
regcache.  This function can be used some targets and these own
$ARCH_{get,set}_pc are replaced by linux_{get,set}_pc_32bit
respectively.

This patch touches many targets, but I only have arm board to
test and no regression.  I also rebuilt nios2-linux GDBserver.
If it is right to go, I'll post the 64-bit counterpart later.

gdb/gdbserver:

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

	* linux-arm-low.c (debug_threads): Remove declaration.
	(arm_get_pc, arm_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-bfin-low.c (bfin_get_pc, bfin_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-cris-low.c (debug_threads): Remove declaration.
	(cris_get_pc, cris_set_pc,): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-crisv32-low.c (debug_threads): Remove declaration.
	(cris_get_pc, cris_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-low.c: Include inttypes.h.
	(linux_get_pc_32bit, linux_set_pc_32bit): New functions.
	* linux-low.h (linux_get_pc_32bit, linux_set_pc_32bit): Declare.
	* linux-m32r-low.c (m32r_get_pc, m32r_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-m68k-low.c (m68k_get_pc, m68k_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-nios2-low.c (nios2_get_pc, nios2_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-sh-low.c (sh_get_pc, sh_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-xtensa-low.c (xtensa_get_pc, xtensa_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_64bit
@ 2016-01-18 15:19 sergiodj+buildbot
  2016-01-18 18:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f69e520676f5f434cf43c250865036b3d516429 ***

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

Replace some $ARCH_{get,set}_pc with linux_{get,set}_pc_64bit

This patch is the follow-up of
https://sourceware.org/ml/gdb-patches/2016-01/msg00164.html to provide
linux_{get,set}_pc_64bit functions.

Rebuild GDBserver with tilegx-linux-gcc.  Not tested.

I think about pc in Tile-GX a little bit.  Looks current Tile-GX
supports debugging 32-bit program (multi-arch), but PC is always
64-bit.  See this thread
https://sourceware.org/ml/gdb-patches/2013-02/msg00113.html
and GDBserver reads PC as 64-bit through ptrace.  However, if
the inferior is 32-bit, the PC in the target description and
regcache is 32-bit, so only 32-bit contents are sent back GDB.
Anyway, Tile-GX GDBserver may have some problems here, but this
patch doesn't change anything.

gdb/gdbserver:

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

	* linux-low.c (linux_set_pc_64bit): New function.
	(linux_get_pc_64bit): New function.
	* linux-low.h (linux_set_pc_64bit, linux_get_pc_64bit):
	Declare.
	* linux-sparc-low.c (debug_threads): Remove declaration.
	(sparc_get_pc): Remove.
	(the_low_target): Use linux_get_pc_64bit instead of
	sparc_get_pc.
	* linux-tile-low.c (tile_get_pc, tile_set_pc): Remove.
	(the_low_target): Use linux_get_pc_64bit and
	linux_set_pc_64bit.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR threads/19422 - show which thread caused stop
@ 2016-01-18 16:03 sergiodj+buildbot
  2016-01-18 19:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f303dbd60d9c7984832446eeb9d4e4d89703c615 ***

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

Fix PR threads/19422 - show which thread caused stop

This commit changes GDB like this:

 - Program received signal SIGINT, Interrupt.
 + Thread 1 "main" received signal SIGINT, Interrupt.

 - Breakpoint 1 at 0x40087a: file threads.c, line 87.
 + Thread 3 "bar" hit Breakpoint 1 at 0x40087a: file threads.c, line 87.

 ... once the program goes multi-threaded.  Until GDB sees a second
thread spawn, the output is still the same as before, per the
discussion back in 2012:

  https://www.sourceware.org/ml/gdb/2012-11/msg00010.html

This helps non-stop mode, where you can't easily tell which thread hit
a breakpoint or received a signal:

 (gdb) info threads
   Id   Target Id         Frame
 * 1    Thread 0x7ffff7fc1740 (LWP 19362) "main" (running)
   2    Thread 0x7ffff7fc0700 (LWP 19366) "foo" (running)
   3    Thread 0x7ffff77bf700 (LWP 19367) "bar" (running)
 (gdb)
 Program received signal SIGUSR1, User defined signal 1.
 0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
 92          lll_wait_tid (pd->tid);
 (gdb) b threads.c:87
 Breakpoint 1 at 0x40087a: file threads.c, line 87.
 (gdb)
 Breakpoint 1, thread_function1 (arg=0x1) at threads.c:87
 87              usleep (1);  /* Loop increment.  */

The best the user can do is run "info threads" and try to figure
things out.

It actually also affects all-stop mode, in case of "handle SIG print
nostop":

...
  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.
...

The above doesn't give any clue that these were different threads
getting the SIGUSR1 signal.

I initially thought of lowercasing "breakpoint" in

  "Thread 3 hit Breakpoint 1"

but then after trying it I realized that leaving "Breakpoint"
uppercase helps the eye quickly find the relevant information.  It's
also easier to implement not showing anything about threads until the
program goes multi-threaded this way.

Here's a larger example session in non-stop mode:

  (gdb) c -a&
  Continuing.
  (gdb) interrupt -a
  (gdb)
  Thread 1 "main" stopped.
  0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
  92          lll_wait_tid (pd->tid);

  Thread 2 "foo" stopped.
  0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)

  Thread 3 "bar" stopped.
  0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
  b threads.c:87
  Breakpoint 4 at 0x40087a: file threads.c, line 87.
  (gdb) b threads.c:67
  Breakpoint 5 at 0x400811: file threads.c, line 67.
  (gdb) c -a&
  Continuing.
  (gdb)
  Thread 3 "bar" hit Breakpoint 4, thread_function1 (arg=0x1) at threads.c:87
  87              usleep (1);  /* Loop increment.  */

  Thread 2 "foo" hit Breakpoint 5, thread_function0 (arg=0x0) at threads.c:68
  68              (*myp) ++;
  info threads
    Id   Target Id         Frame
  * 1  Thread 0x7ffff7fc1740 (LWP 31957) "main" (running)
    2  Thread 0x7ffff7fc0700 (LWP 31961) "foo" thread_function0 (arg=0x0) at threads.c:68
    3  Thread 0x7ffff77bf700 (LWP 31962) "bar" thread_function1 (arg=0x1) at threads.c:87
  (gdb) shell kill -SIGINT 31957
  (gdb)
  Thread 1 "main" received signal SIGINT, Interrupt.
  0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
  92          lll_wait_tid (pd->tid);
  info threads
    Id   Target Id         Frame
  * 1  Thread 0x7ffff7fc1740 (LWP 31957) "main" 0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
    2  Thread 0x7ffff7fc0700 (LWP 31961) "foo" thread_function0 (arg=0x0) at threads.c:68
    3  Thread 0x7ffff77bf700 (LWP 31962) "bar" thread_function1 (arg=0x1) at threads.c:87
  (gdb) t 2
  [Switching to thread 2, Thread 0x7ffff7fc0700 (LWP 31961)]
  #0  thread_function0 (arg=0x0) at threads.c:68
  68              (*myp) ++;
  (gdb) catch syscall
  Catchpoint 6 (any syscall)
  (gdb) c&
  Continuing.
  (gdb)
  Thread 2 "foo" hit Catchpoint 6 (call to syscall nanosleep), 0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)

I'll work on documentation next if this looks agreeable.

This patch applies on top of the star wildcards thread IDs series:

  https://sourceware.org/ml/gdb-patches/2016-01/msg00291.html

For convenience, I've pushed this to the
users/palves/show-which-thread-caused-stop branch.

gdb/doc/ChangeLog:
2016-01-18  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Threads): Mention that GDB displays the ID and name
	of the thread that hit a breakpoint or received a signal.

gdb/ChangeLog:
2016-01-18  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention that GDB now displays the ID and name of the
	thread that hit a breakpoint or received a signal.
	* break-catch-sig.c (signal_catchpoint_print_it): Use
	maybe_print_thread_hit_breakpoint.
	* break-catch-syscall.c (print_it_catch_syscall): Likewise.
	* break-catch-throw.c (print_it_exception_catchpoint): Likewise.
	* breakpoint.c (maybe_print_thread_hit_breakpoint): New function.
	(print_it_catch_fork, print_it_catch_vfork, print_it_catch_solib)
	(print_it_catch_exec, print_it_ranged_breakpoint)
	(print_it_watchpoint, print_it_masked_watchpoint, bkpt_print_it):
	Use maybe_print_thread_hit_breakpoint.
	* breakpoint.h (maybe_print_thread_hit_breakpoint): Declare.
	* gdbthread.h (show_thread_that_caused_stop): Declare.
	* infrun.c (print_signal_received_reason): Print which thread
	received signal.
	* thread.c (show_thread_that_caused_stop): New function.

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

	* gdb.base/async-shell.exp: Adjust expected output.
	* gdb.base/dprintf-non-stop.exp: Adjust expected output.
	* gdb.base/siginfo-thread.exp: Adjust expected output.
	* gdb.base/watchpoint-hw-hit-once.exp: Adjust expected output.
	* gdb.java/jnpe.exp: Adjust expected output.
	* gdb.threads/clone-new-thread-event.exp: Adjust expected output.
	* gdb.threads/continue-pending-status.exp: Adjust expected output.
	* gdb.threads/leader-exit.exp: Adjust expected output.
	* gdb.threads/manythreads.exp: Adjust expected output.
	* gdb.threads/pthreads.exp: Adjust expected output.
	* gdb.threads/schedlock.exp: Adjust expected output.
	* gdb.threads/siginfo-threads.exp: Adjust expected output.
	* gdb.threads/signal-command-multiple-signals-pending.exp: Adjust
	expected output.
	* gdb.threads/signal-delivered-right-thread.exp: Adjust expected
	output.
	* gdb.threads/sigthread.exp: Adjust expected output.
	* gdb.threads/watchpoint-fork.exp: Adjust expected output.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use a 32-bit value to hold the section number in the internal COFF symbol structure.
@ 2016-01-18 16:11 sergiodj+buildbot
  2016-01-18 21:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 16:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ae678af999b8a692c4e6efbe493f39f0085d149 ***

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

Use a 32-bit value to hold the section number in the internal COFF symbol structure.

	PR ld/19440
inc	* coff/internal.h (internal_syment): Use int to hold section
	number.
	(N_UNDEF): Cast to int not short.
	(N_ABS): Likewise.
	(N_DEBUG): Likewise.
	(N_TV): Likewise.
	(P_TV): Likewise.

bfd	PR ld/19440
	* coff-rs6000.c (_bfd_xcoff_swap_sym_in): Sign extend external
	section number into internal section number.
	* coff64-rs6000.c (_bfd_xcoff64_swap_sym_in): Likewise.
	* coffswap.h (coff_swap_sym_in): Likewise.
	* peXXigen.c (_bfd_XXi_swap_sym_in): Likewise.
	* coffcode.h (_coff_bigobj_swap_sym_in): Make sure that internal
	section number field is big enough to hold the external value.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Remove unused global references in gdb_test
@ 2016-01-18 17:08 sergiodj+buildbot
  2016-01-18 22:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8bcbad33671aa67a0079fe4f8f448458de8cc05f ***

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

testsuite: Remove unused global references in gdb_test

Those are unused since gdb_test_multiple was added, factoring out most
of the content of gdb_test.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (gdb_test): Remove unused global references.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS: Fix microMIPS instruction size determination
@ 2016-01-18 21:22 sergiodj+buildbot
  2016-01-19  0:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 21:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f7f365076a112313870e2a321452bfda6d40914 ***

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

MIPS: Fix microMIPS instruction size determination

Fix a bug in `micromips_insn_at_pc_has_delay_slot' in instruction size
determination via `mips_insn_size'.  In the microMIPS case the latter
function expects a lone 16-bit instruction word containing the major
opcode regardless of whether the opcode requires another 16-bit word to
follow, to form a complete 32-bit instruction.  Code however passes the
16-bit word previously retrieved shifted left by 16 bits.  Consequently
`mips_insn_size', which examines the low 16-bit only, always sees 0.

By pure coincidence a major opcode of 0 denotes a 32-bit instruction in
the microMIPS instruction set, so the size of 4 is always returned here,
and the following 16-bit word is then merged in the low 16 bits of the
instruction previously shifted by 16 bits.  The resulting 32-bit value
is then passed to `micromips_instruction_has_delay_slot' for delay slot
presence determination.  This function in turn first examines the high
16 bits of the instruction word received and ignores the low 16 bits for
16-bit instructions.

Consequently the only effect of this bug is an extraneous memory read
issued to retrieve a subsequent 16-bit word where a 16-bit instruction
is being examined.  Which in turn may fail if the instruction is located
right at the end of a readable memory area, in which case the lack of a
delay slot will be reported to the caller, which may be incorrect.

This code is used in breakpoint maintenance, for delay slot avoidance,
so the bug would only trigger for the unlikely case of someone placing
a breakpoint in a delay slot of an instruction which is at the end of
readable memory.  Which explains why the bug remained unnoticed so long.

	gdb/
	* mips-tdep.c (micromips_insn_at_pc_has_delay_slot): Pass
	unshifted 16-bit microMIPS instruction word to `mips_insn_size'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS: Only build microMIPS specific simulator functions if microMIPS support is required.
@ 2016-01-18 22:01 sergiodj+buildbot
  2016-01-19  1:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 22:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d304f48cafbff4b7a1c0a9d338fb20aa4e4934b ***

Author: Andrew Bennett <andrew.bennett@imgtec.com>
Branch: master
Commit: 3d304f48cafbff4b7a1c0a9d338fb20aa4e4934b

MIPS: Only build microMIPS specific simulator functions if microMIPS support is required.

This fixes PR sim/19441.  In the MIPS simulator the microMIPS
functions in micromips.igen were not predicated on the microMIPS
models.  This was causing build issues for some target triples.
This patch sets all the microMIPS specific functions to only be built if
the micromips32, micromips64 or micromipsdsp models are used.

	PR sim/19441
	* micromips.igen (delayslot_micromips): Enable for `micromips32',
	`micromips64' and `micromipsdsp' only.
	(process_isa_mode): Enable for `micromips32' and `micromips64' only.
	(do_micromips_jalr, do_micromips_jal): Likewise.
	(compute_movep_src_reg): Likewise.
	(compute_andi16_imm): Likewise.
	(convert_fmt_micromips): Likewise.
	(convert_fmt_micromips_cvt_d): Likewise.
	(convert_fmt_micromips_cvt_s): Likewise.
	(FMT_MICROMIPS): Likewise.
	(FMT_MICROMIPS_CVT_D): Likewise.
	(FMT_MICROMIPS_CVT_S): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS: Remove remnants of 48-bit microMIPS instruction support
@ 2016-01-18 22:31 sergiodj+buildbot
  2016-01-19  2:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 22:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 100b4f2e9f65565e3e3e484162c4474effc54be8 ***

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

MIPS: Remove remnants of 48-bit microMIPS instruction support

The POOL48A major opcode was defined in early revisions of the 64-bit
microMIPS ISA, has never been implemented, and was removed before the
64-bit microMIPS ISA specification[1] has been finalized.

This complements commit a6c7053929dd ("MIPS/opcodes: Remove microMIPS
48-bit LI instruction").

References:

[1] "MIPS Architecture for Programmers, Volume II-B: The microMIPS64
    Instruction Set", MIPS Technologies, Inc., Document Number: MD00594,
    Revision 3.06, October 17, 2012, Table 6.2 "microMIPS64 Encoding of
    Major Opcode Field", p. 578

	gas/
	* config/tc-mips.c (micromips_insn_length): Remove the mention
	of 48-bit microMIPS instructions.

	gdb/
	* mips-tdep.c (mips_insn_size): Remove 48-bit microMIPS
	instruction support.
	(micromips_next_pc): Likewise.
	(micromips_scan_prologue): Likewise.
	(micromips_deal_with_atomic_sequence): Likewise.
	(micromips_stack_frame_destroyed_p): Likewise.
	(mips_breakpoint_from_pc): Likewise.

	opcodes/
	* mips-dis.c (print_insn_micromips): Remove 48-bit microMIPS
	instruction support.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Limit breakpoint re-set to the current program space
@ 2016-01-19 12:38 sergiodj+buildbot
  2016-01-19 15:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 12:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2f4122d5cc2a21a441470336c8637b6a6965c6e ***

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

Limit breakpoint re-set to the current program space

Currently, we always re-set all locations of all breakpoints.  This
commit makes us re-set only locations of the current program space.

If we loaded symbols to a program space (e.g., "file" command or some
shared library was loaded), GDB must run through all breakpoints and
determine if any new locations need to be added to the breakpoint.
However, there's no reason to recreate locations for _other_ program
spaces, as those haven't changed.

Similarly, when we create a new inferior, through e.g., a fork, GDB
must run through all breakpoints and determine if any new locations
need to be added to the breakpoint.  There's no reason to destroy the
locations of the parent inferior and other inferiors.  We know those
won't change.

In addition to being inneficient, resetting breakpoints of inferiors
that are currently running is problematic, because:

 - some targets can't read memory while the inferior is running.

 - the inferior might exit while we're re-setting its breakpoints,
   which may confuse prologue skipping.

I went through all the places where we call breakpoint_re_set, and it
seems to me that all can be changed to only re-set locations of the
current program space.

The patch that reversed threads order in "info threads" etc. happened
to make gdb.threads/fork-plus-thread.exp expose this problem when
testing on x86/-m32.  The problem was latent and masked out by chance
by the code-cache:

 https://sourceware.org/ml/gdb-patches/2016-01/msg00213.html

Tested on x86-64 F20, native (-m64/-m32) and extended-remote
gdbserver.

Fixes the regression discussed in the url above with --target_board=unix/-m32:

 -FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: inferior 1 exited
 +PASS: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: inferior 1 exited
 -FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: no threads left (timeout)
 -FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: only inferior 1 left (the program exited)
 +PASS: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: no threads left
 +PASS: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: only inferior 1 left

gdb/ChangeLog:
2016-01-19  Pedro Alves  <palves@redhat.com>

	* ax-gdb.c (agent_command_1): Adjust call to decode_line_full.
	* break-catch-throw.c (re_set_exception_catchpoint): Pass the
	current program space down to linespec decoding and breakpoint
	location updating.
	* breakpoint.c (parse_breakpoint_sals): Adjust calls to
	decode_line_full.
	(until_break_command): Adjust calls to decode_line_1.
	(base_breakpoint_decode_location, bkpt_decode_location): Add
	'search_pspace' parameter.  Pass it along.
	(bkpt_probe_create_sals_from_location): Adjust calls to
	parse_probes.
	(tracepoint_decode_location, tracepoint_probe_decode_location)
	(strace_marker_decode_location): Add 'search_pspace' parameter.
	Pass it along.
	(all_locations_are_pending): Rewrite to take a breakpoint and
	program space as arguments instead.
	(hoist_existing_locations): New function.
	(update_breakpoint_locations): Add 'filter_pspace' parameter.  Use
	hoist_existing_locations instead of always removing all locations,
	and adjust to all_locations_are_pending change.
	(location_to_sals): Add 'search_pspace' parameter.  Pass it along.
	Don't disable the breakpoint if there are other locations in
	another program space.
	(breakpoint_re_set_default): Adjust to pass down the current
	program space as filter program space.
	(decode_location_default): Add 'search_pspace' parameter and pass
	it along.
	(prepare_re_set_context): Don't switch program space here.
	(breakpoint_re_set): Use save_current_space_and_thread instead of
	save_current_program_space.
	* breakpoint.h (struct breakpoint_ops) <decode_location>: Add
	'search_pspace' parameter.
	(update_breakpoint_locations): Add 'filter_pspace' parameter.
	* cli/cli-cmds.c (edit_command, list_command): Adjust calls to
	decode_line_1.
	* elfread.c (elf_gnu_ifunc_resolver_return_stop): Pass the current
	program space as filter program space.
	* linespec.c (struct linespec_state) <search_pspace>: New field.
	(create_sals_line_offset, convert_explicit_location_to_sals)
	(parse_linespec): Pass the search program space down.
	(linespec_state_constructor): Add 'search_pspace' parameter.
	Store it.
	(linespec_parser_new): Add 'search_pspace' parameter and pass it
	along.
	(linespec_lex_to_end): Adjust.
	(decode_line_full, decode_line_1): Add 'search_pspace' parameter
	and pass it along.
	(decode_line_with_last_displayed): Adjust.
	(collect_symtabs_from_filename, symtabs_from_filename): New
	'search_pspace' parameter.  Use it.
	(find_function_symbols): Pass the search program space down.
	* linespec.h (decode_line_1, decode_line_full): Add
	'search_pspace' parameter.
	* probe.c (parse_probes_in_pspace): New function, factored out
	from ...
	(parse_probes): ... this.  Add 'search_pspace' parameter and use
	it.
	* probe.h (parse_probes): Add pspace' parameter.
	* python/python.c (gdbpy_decode_line): Adjust.
	* tracepoint.c (scope_info): Adjust.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <bd0a71fa16f668341a9361c695bc3ca44d27b322@gdb-build>]
* [binutils-gdb] Add PIC and TLS support to the ARC target.
@ 2016-01-19 15:37 sergiodj+buildbot
  2016-01-19 16:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 15:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34e967a5f3ac5fd0353731a259e358d462823290 ***

Author: Miranda Cupertino <Cupertino.Miranda@synopsys.com>
Branch: master
Commit: 34e967a5f3ac5fd0353731a259e358d462823290

Add PIC and TLS support to the ARC target.

bfd/ChangeLog:
	* arc-plt.def: New file.
	* arc-plt.h: Likewise.
	* elf32-arc.c (elf_arc_abs_plt0_entry, elf_arc_abs_pltn_entry,
		       elf_arcV2_abs_plt0_entry, elf_arcV2_abs_pltn_entry,
		       elf_arc_pic_plt0_entry, elf_arc_pic_pltn_entry,
		       elf_arcV2_pic_plt0_entry, elf_arcV2_pic_pltn_entry): Remove.
	(name_for_global_symbol): Added.
	(ADD_RELA): Helper to create dynamic relocs.
	(new_got_entry_to_list): Create a new got entry in linked list.
	(symbol_has_entry_of_type): Search for specific type of entry in
	list.
	(is_reloc_for_GOT): return FALSE for any TLS related relocs.
	(is_reloc_for_TLS, arc_elf_set_private_flags)
	(arc_elf_print_private_bfd_data, arc_elf_copy_private_bfd_data)
	(arc_elf_merge_private_bfd_data): New functions.
	(debug_arc_reloc): Cleaned debug info printing.
	(PDATA reloc): Changed not to perform address alignment.
	(reverse_me): Added. Fix for ARC_32 relocs.
	(arc_do_relocation): Return bfd_reloc_of when no relocation should
	occur.
	(arc_get_local_got_ents): Renamed from arc_get_local_got_offsets.
	Changed function to access an array of list of GOT entries instead
	of just an array of offsets.
	(elf_arc_relocate_section): Added support for PIC and TLS related relocations.
	(elf_arc_check_relocs): Likewise.
	(elf_arc_adjust_dynamic_symbol, elf_arc_finish_dynamic_symbol,
	(elf_arc_finish_dynamic_sections): Likewise
	(arc_create_dynamic_sections): Modified conditions to create
	dynamic sections.
	(ADD_SYMBOL_REF_SEC_AND_RELOC): New macro.
	(plt_do_relocs_for_symbol, relocate_plt_for_symbol)
	(relocate_plt_for_entry): Changed to support new way to define PLT
	related code.
	(add_symbol_to_plt): Likewise.
	(arc_elf_link_hash_table_create): New function.

include/ChangeLog:
	* elf/arc-reloc.def (ARC_32, ARC_GOTPC, ARC_TLS_GD_GOT)
	(ARC_TLS_IE_GOT, ARC_TLS_DTPOFF, ARC_TLS_DTPOFF_S9, ARC_TLS_LE_S9)
	(ARC_TLS_LE_32): Fixed formula.
	(ARC_TLS_GD_LD): Use new special function.
	* opcode/arc-func.h: Changed all the replacement
	functions to clear the patching bits before doing an or it with the value
	argument.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix detection of "r_fs" and "r_gs" on FreeBSD.
@ 2016-01-19 15:50 sergiodj+buildbot
  2016-01-19 18:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6e69c1f1de84549d99792031dd05d5ba70bd8a5 ***

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

Fix detection of "r_fs" and "r_gs" on FreeBSD.

Include <sys/types.h> as a prerequisite for <machine/reg.h> when checking
for the r_fs and r_gs members in struct reg.  Note that the previous test
for <machine/reg.h> already includes <sys/types.h> as a prerequisite.

gdb/ChangeLog:

	* configure.ac: Include <sys/types.h when checking for "r_fs" in
	"struct reg".
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Make check-parallel return non-zero if a test failed
@ 2016-01-19 15:58 sergiodj+buildbot
  2016-01-19 19:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 15:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bef95aacb8501edb086381b3d413485d732f00f3 ***

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

testsuite: Make check-parallel return non-zero if a test failed

When using the check-parallel target, the return code of make is always 0,
regardless of test results.  This patch makes it return the same code as
the "make do-check-parallel" sub-command.  So if there is a FAIL somewhere,
non-zero will be returned by make.

For the sake of example, I introduced a failure in gdb.base/break.exp.

  $ make check-single TESTS="gdb.base/break.exp gdb.python/py-value.exp" && echo 'Success :D' || echo 'Fail :('
  ...
  FAIL: gdb.base/break.exp: allo
  ...
  Fail :(

I think the parallel run should do the same.  Currently:

  $ make check-parallel TESTS="gdb.base/break.exp gdb.python/py-value.exp" && echo 'Success :D' || echo 'Fail :('
  ...
  FAIL: gdb.base/break.exp: allo
  ...
  Success :D

And with the patch (no big surprises there):

  $ make check-parallel TESTS="gdb.base/break.exp gdb.python/py-value.exp" && echo 'Success :D' || echo 'Fail :('
  ...
  FAIL: gdb.base/break.exp: allo
  ...
  Fail :(

What do you think?

gdb/testsuite/ChangeLog:

	* Makefile.in (check-parallel): Propagate return code from make
	do-check-parallel.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Add --status to runtest invocation
@ 2016-01-19 16:07 sergiodj+buildbot
  2016-01-19 20:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 16:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10eadbcc2866f11bd93ef379c76524521abdc218 ***

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

testsuite: Add --status to runtest invocation

By default, if a test driver (a test .exp) ends with an uncaught
error/exception, the runtest command will still have a return code of 0
(success).  However, if a test (or the environment) is broken and does
not work properly, it should be considered as failed so that we can
notice it and fix it.

Passing the --status flag to runtest will make it return an error if one
of the test it runs ends up with an uncaught error.

gdb/testsuite/ChangeLog:

	* Makefile.in (check-single): Pass --status to runtest.
	(check/%.exp): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Factor out --status in DO_RUNTEST
@ 2016-01-19 16:35 sergiodj+buildbot
  2016-01-19 22:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41d1845edace3cf5dabd0aa7fa376b801fd5f675 ***

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

testsuite: Factor out --status in DO_RUNTEST

gdb/testsuite/ChangeLog:

	* Makefile.in (DO_RUNTEST): Add --status and update usages.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix enum flag with Python 3
@ 2016-01-19 16:43 sergiodj+buildbot
  2016-01-19 23:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 16:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10e3ed9029dc0b6eafcd991d9f292fc079f80cf5 ***

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

Fix enum flag with Python 3

Using Python 3.5 (I assume it's the same with 3.4 and lower, but I didn't
test), I see this:

  print (enum flag_enum) (FLAG_1)^M
  Python Exception <class 'TypeError'> %x format: an integer is required, not gdb.Value: ^M
  $7 = ^M
  (gdb) FAIL: gdb.python/py-pp-maint.exp: print FLAG_1

Apparently, this idiom, where v is a gdb.Value, was possible with Python 2,
but not with Python 3:

  '%x' % v

In Python 2, it would automatically get converted to an integer.  To solve
it, I simply added wrapped v in a call to int().

  '%x' % int(v)

In Python 2, the int type is implemented with a "long" in C, so on x86-32 it's
32-bits.  I was worried that doing int(v) would truncate the value and give
wrong results for enum values > 32-bits.  However, the int type != the int
function.  The int function does the right thing, selecting the right integer
type for the given value.  I tested with large enum values on x86-32 and
Python 2, and everything works as expected.

gdb/ChangeLog:

	* python/lib/gdb/printing.py (_EnumInstance.to_string): Explicitly
	convert gdb.Value to integer type using int().


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support to readelf for reading FreeBSD ELF core notes.
@ 2016-01-19 17:09 sergiodj+buildbot
  2016-01-20  0:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4ddf30f1108b2c0b3eee5677c912383ac903256 ***

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

Add support to readelf for reading FreeBSD ELF core notes.

binutils/ChangeLog:

	* readelf.c (get_freebsd_elfcore_note_type): New
	(process_note): Add support for FreeBSD core notes.

include/ChangeLog:

	* elf/common.h (NT_FREEBSD_THRMISC): Define.
	(NT_FREEBSD_PROCSTAT_PROC): Define.
	(NT_FREEBSD_PROCSTAT_FILES): Define.
	(NT_FREEBSD_PROCSTAT_VMMAP): Define.
	(NT_FREEBSD_PROCSTAT_GROUPS): Define.
	(NT_FREEBSD_PROCSTAT_UMASK): Define.
	(NT_FREEBSD_PROCSTAT_RLIMIT): Define.
	(NT_FREEBSD_PROCSTAT_OSREL): Define.
	(NT_FREEBSD_PROCSTAT_PSSTRINGS): Define.
	(NT_FREEBSD_PROCSTAT_AUXV): Define.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add a pseudosection for the NT_FREEBSD_THRMISC note.
@ 2016-01-19 17:18 sergiodj+buildbot
  2016-01-20  2:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b2c414df12bb61ab1e40099b92fc8f00983b930 ***

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

Add a pseudosection for the NT_FREEBSD_THRMISC note.

bfd/ChangeLog:

	* elf.c (elfcore_grok_note): Recognize NT_FREEBSD_THRMISC notes.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for extracting thread names from cores.
@ 2016-01-19 17:26 sergiodj+buildbot
  2016-01-20  3:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dfc5dbc4e1b267d440dd515a42fe6fd96a8d860 ***

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

Add support for extracting thread names from cores.

Add a new gdbarch method to extract a thread name from a core for a
given thread.  Use this new method in core_thread_name to implement the
to_thread_name target op.

gdb/ChangeLog:

	* corelow.c (core_thread_name): New function.
	(init_core_ops): Use "core_thread_name" for the "to_thread_name"
	target op.
	* gdbarch.sh (core_thread_name): New gdbarch callback.
	* gdbarch.h: Re-generate.
	* gdbarch.c: Re-generate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Display per-thread information for threads in FreeBSD cores.
@ 2016-01-19 17:34 sergiodj+buildbot
  2016-01-20  4:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 791174281c341539fab650bd934cc0060b7c9720 ***

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

Display per-thread information for threads in FreeBSD cores.

Display the LWP ID of each thread in a FreeBSD core.  Extract thread
names from the per-thread THRMISC note.

gdb/ChangeLog:

	* fbsd_tdep.c (fbsd_core_pid_to_str): New function.
	(fbsd_core_thread_name): New function.
	(fbsd_init_abi): Add "core_pid_to_str" gdbarch method.
	Add "core_thread_name" gdbarch method.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use LWP IDs with ptrace register requests on FreeBSD.
@ 2016-01-19 17:43 sergiodj+buildbot
  2016-01-20  6:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94309df7aa9ab48bec7fb58fdc1deb26e24fc4c1 ***

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

Use LWP IDs with ptrace register requests on FreeBSD.

This allows gdb to fetch per-thread registers for multi-threaded FreeBSD
processes.

Export get_ptrace_pid() from inf-ptrace.c and use it to determine the PID
to pass to ptrace in pan-BSD native targets.  NetBSD and OpenBSD also accept
LWP IDs for ptrace requests to fetch per-thread state.

gdb/ChangeLog:

	* amd64bsd-nat.c (amd64bsd_fetch_inferior_registers): Use
	get_ptrace_pid.
	(amd64bsd_store_inferior_registers): Use get_ptrace_pid.
	(amd64bsd_dr_get): Use get_ptrace_pid.
	(amd64bsd_dr_set): Use get_ptrace_pid.
	* i386bsd-nat.c (i386bsd_fetch_inferior_registers): Use get_ptrace_pid.
	(i386bsd_store_inferior_registers): Use get_ptrace_pid.
	(i386bsd_dr_get): Use get_ptrace_pid.
	(i386bsd_dr_set): Use get_ptrace_pid.
	* inf-ptrace.c (get_ptrace_pid): Export.
	* inf-ptrace.h (get_ptrace_pid): Declare.
	* ppcfbsd-nat.c (ppcfbsd_fetch_inferior_registers): Use lwp id.
	(ppcfbsd_store_inferior_registers): Use lwp id.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for LWP-based threads on FreeBSD.
@ 2016-01-19 17:51 sergiodj+buildbot
  2016-01-20  7:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e9567fe2ab39d1de89ecc5105c17443b66c9b48 ***

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

Add support for LWP-based threads on FreeBSD.

Older versions of FreeBSD supported userland threading via a pure
user-space threading library (N threads scheduled on 1 process) and
a N:M model (N threads scheduled on M LWPs).  However, modern FreeBSD
versions only support a M:M threading model where each user thread is
backed by a dedicated LWP.  This thread target only supports this
threading model.  It also uses ptrace to query and alter LWP state
directly rather than using libthread_db to simplify the implementation.

FreeBSD recently gained support for reporting LWP events (birth and death
of LWPs).  GDB will use LWP events when present.  For older systems it
fetches the list of LWPs in the to_update_thread_list target op to update
the list of threads on each stop.

This target supports scheduler locking by using ptrace to suspend
individual LWPs as necessary before resuming a process.

gdb/ChangeLog:

	* configure.ac: Check for support for LWP names on FreeBSD.
	* fbsd-nat.c [PT_LWPINFO] New variable debug_fbsd_lwp.
	[TDP_RFPPWAIT || HAVE_STRUCT_PTRACE_LWPINFO_PL_TDNAME]
	(fbsd_fetch_kinfo_proc): Move function earlier.
	[PT_LWPINFO] (fbsd_thread_alive): New function.
	[PT_LWPINFO] (fbsd_pid_to_str): New function.
	[HAVE_STRUCT_PTRACE_LWPINFO_PL_TDNAME] (fbsd_thread_name): New function.
	[PT_LWP_EVENTS] (fbsd_enable_lwp_events): New function.
	[PT_LWPINFO] (fbsd_add_threads): New function.
	[PT_LWPINFO] (fbsd_update_thread_list): New function.
	[PT_LWPINFO] New variable super_resume.
	[PT_LWPINFO] (resume_one_thread_cb): New function.
	[PT_LWPINFO] (resume_all_threads_cb): New function.
	[PT_LWPINFO] (fbsd_resume): New function.
	(fbsd_remember_child): Save full ptid instead of plain pid.
	(fbsd_is_child_pending): Return ptid of saved child process.
	(fbsd_wait): Include lwp in returned ptid and switch to LWP ptid on
	first stop.
	[PT_LWP_EVENTS] Handle LWP events.
	[TDP_RFPPWAIT] Include LWP in child ptid.
	(fbsd_post_startup_inferior) [PT_LWP_EVENTS]: Enable LWP events.
	(fbsd_post_attach) [PT_LWP_EVENTS]: Enable LWP events.
	Add threads for existing processes.
	(fbsd_nat_add_target) [PT_LWPINFO]: Set "to_thread_alive" to
	"fbsd_thread_alive".
	Set "to_pid_to_str" to "fbsd_pid_to_str".
	[HAVE_STRUCT_PTRACE_LWPINFO_PL_TDNAME]: Set "to_thread_name" to
	"fbsd_thread_name".
	[PT_LWPINFO]: Set "to_update_thread_list" to "fbsd_update_thread_list".
	Set "to_has_thread_control" to "tc_schedlock".
	Set "to_resume" to "fbsd_resume".
	(_initialize_fbsd_nat): New function.
	* configure: Regenerate.
	* config.in: Regenerate.

gdb/doc/ChangeLog:

	* gdb.texinfo (Debugging Output): Document "set/show debug fbsd-lwp".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Dump register notes for each thread when generating a FreeBSD core.
@ 2016-01-19 18:00 sergiodj+buildbot
  2016-01-20  8:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 18:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20a0aab3ed0f4bb5c304e560751b09b7b82a3e65 ***

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

Dump register notes for each thread when generating a FreeBSD core.

gdb/ChangeLog:

	* fbsd-tdep.c (find_stop_signal): Remove.
	(struct fbsd_collect_regset_section_cb) <lwp>: New field.
	<stop_signal>: New field.
	<abort_iteration>: New field.
	(fbsd_collect_regset_section_cb): Use new fields.
	(fbsd_collect_thread_registers): New function.
	(struct fbsd_corefile_thread_data): New structure.
	(fbsd_corefile_thread): New function.
	(fbsd_make_corefile_notes): Use new function to dump notes for each
	non-exited thread in a process.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use a separate variable for the size passed to sysctl.
@ 2016-01-19 23:43 sergiodj+buildbot
  2016-01-20 10:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 23:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2feec9809edbeeee0bb5b036e4ae25f9c37cd14 ***

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

Use a separate variable for the size passed to sysctl.

This fixes a sign mismatch warning.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_pid_to_exec_file): Use new "buflen" instead of
	"len" with sysctl.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] minor reformatting in printcmd.c::print_scalar_formatted
@ 2016-01-20  4:14 sergiodj+buildbot
  2016-01-20 11:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-20  4:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be56871ee8f65c51b9eee611532ed036a71a72e0 ***

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

minor reformatting in printcmd.c::print_scalar_formatted

(GNU Coding Standard...)

gdb/ChangeLog:

        * printcmd.c (print_scalar_formatted): move binary operator from
        end of line to beginning of next line.  Adjust formatting
        accordingly.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD.
@ 2016-01-20 13:05 sergiodj+buildbot
  2016-01-20 14:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91f68a68f992e3f6c3da26c616b5257230bd1eec ***

Author: Mickael Guene <mickael.guene@st.com>
Branch: master
Commit: 91f68a68f992e3f6c3da26c616b5257230bd1eec

Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD.

bfd/ChangeLog:
      * elf32-arm.c ((elf32_arm_special_sections): Remove catch of noread
      section using '.text.noread' pattern.

gas/ChangeLog:
      * config/obj-elf.c (obj_elf_change_section) : Allow arm section with
      SHF_ARM_NOREAD section flag.
      * config/tc-arm.h (md_elf_section_letter) : Implement this hook to
      handle letter 'y'.
     (arm_elf_section_letter) : Declare it.
      * config/tc-arm.c (arm_elf_section_letter): Handle letter 'y' to set
      SHF_ARM_NOREAD section flag.
      * doc/c-arm.texi (ARM section attribute 'y'): Document it.

gas/testsuite/ChangeLog:
      * gas/arm/section-execute-only.s: New test case.
      * gas/arm/section-execute-only.d: Expected output.

ld/testsuite/ChangeLog:
      * ld-arm/thumb1-noread-not-present-mixing-two-section.s: Add 'y'
      attribute usage.
      * ld-arm/thumb1-noread-present-one-section.s: Likewise.
      * ld-arm/thumb1-noread-present-two-section.s: Likewise.
      * ld-arm/thumb1-input-section-flag-match.s: Likewise.

binutils/ChangeLog:
      * readelf.c (get_elf_section_flags): Display y letter for section
      with SHF_ARM_NOREAD section flag in readelf section output.
      (process_section_headers): Add y letter in readelf section output
      key mapping for ARM architecture.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR UAO
@ 2016-01-20 14:43 sergiodj+buildbot
  2016-01-20 15:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bff6e2d6942690d81ce1f33728de07835b0f5b7 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 0bff6e2d6942690d81ce1f33728de07835b0f5b7

[AArch64] Reject invalid immediate operands to MSR UAO

In the instruction to write to the ARMv8.2 PSTATE field UAO,
MSR UAO, #<imm>, the immediate should be either 0 or 1 but GAS accepts
any unsigned 4-bit integer.

This patch implements the constraint on the immediate, generating an
error if the immediate operand is invalid, and adds tests for the
illegal forms.

opcodes/
2016-01-20  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (operand_general_constraint_met_p): Check validity
	of MSR UAO immediate operand.

gas/
2016-01-20  Matthew Wahab  <matthew.wahab@arm.com>

	* testsuite/gas/aarch64/armv8_2-a-illegal.d: New.
	* testsuite/gas/aarch64/armv8_2-a-illegal.l: New.
	* testsuite/gas/aarch64/armv8_2-a-illegal.s: New.

Change-Id: Ibdec4967c00b1ef3be9dbc43d23b2c70d1a0b28c


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix missing IPA lib in tspeed.exp in some configurations.
@ 2016-01-20 17:40 sergiodj+buildbot
  2016-01-20 18:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9df22175e153e1a8784afb85fc24983adf346171 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 9df22175e153e1a8784afb85fc24983adf346171

Fix missing IPA lib in tspeed.exp in some configurations.

On Ubuntu 14.04 the following failure would be seen when running the
tspeed.exp test on a target that supports fast tracepoints like x86_64:

Target returns error code '.In-process agent library not loaded in
process.  Fast and static tracepoints unavailable.'.
(gdb) FAIL: gdb.trace/tspeed.exp: start trace experiment

This is because the default is to link with --as-needed and the
gdb_compile for the test is using the libs argument instead of shlib which
corrects this issue since 6ebea266fd0a7a56c90db3ab6237ff9f6c919747 by
adding -Wl,--no-as-needed.

This patch fixes the issue by passing the lib as the shlib argument to
gdb_compile.

Tested on Ubuntu 14.04 x86_64.

gdb/testsuite/ChangeLog:

	* gdb.trace/tspeed.exp:  Use shlib instead of libs in gdb_compile
	command.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gnu_vector.exp: Respect `should_kfail' for PR 8549
@ 2016-01-20 18:53 sergiodj+buildbot
  2016-01-20 20:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd356fa28834fa3a9f22f9157a568264ad045010 ***

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

gnu_vector.exp: Respect `should_kfail' for PR 8549

The gnu_vector test case yields a new FAIL on s390x:

  FAIL: gdb.base/gnu_vector.exp: verify vector return value

It was introduced by commit 77ae9c1933b50 "gdb.base/gnu_vector.exp:
Don't test output from the inferior".  That commit dropped the special
handling for GDB's inability (on some targets) to set the return value.

This change re-establishes the logic from before, converting the above
FAIL to a KFAIL (PRMS gdb/8549).

gdb/testsuite/ChangeLog:

	* gdb.base/gnu_vector.exp: Re-establish handling for should_kfail
	when GDB can not set the vector return value.  Add more comments
	for clarification.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix sorting of enum values in FlagEnumerationPrinter
@ 2016-01-20 19:03 sergiodj+buildbot
  2016-01-20 21:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 19:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f5dfff63f31511db45278f97dc22059325ec4d6 ***

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

Fix sorting of enum values in FlagEnumerationPrinter

The lambda function used to sort the enumerator list does not work
properly.  This list consists of tuples, (enum label, enum value).  The
key function returns x.enumval.  enumval not being defined for a tuple,
we see this exception in the test log:

  Python Exception <class 'AttributeError'> 'tuple' object has no attribute 'enumval'

The function should return the second item of the tuple, which is the
enumval.

The pretty-printer still worked mostly correctly, except that the
enumeration values were not sorted.  The test still passed because the
enumeration values are already sorted where they are defined.  The test
also passed despite the exception being printed, because the right output
was printed after the exception:

  print (enum flag_enum) (FLAG_1)
  Python Exception <type 'exceptions.AttributeError'> 'tuple' objecthas no attribute 'enumval':M
  $7 = 0x1 [FLAG_1]
  (gdb) PASS: gdb.python/py-pp-maint.exp: print FLAG_1

New in v2:

- Improved test case, I stole Pedro's example directly.  It verifies
  that the sorting of enumerators by value works, by checking that
  printing FOO_MASK appears as FOO_1 | FOO_2 | FOO_3.

  I noticed that I could change the regexps to almost anything and the
  tests would still pass.  I think it was because of the | in there.  I
  made them more robust by using string_to_regexp.  I used curly braces
  { } instead of quoting marks " " for strings, so that I could use
  square brackets [ ] in them without having to escape them all.  I also
  removed the "message" part of the tests, since they are redundant with
  the command, and it's just more maintenance to have to update them.

  Tested with Python 2.7 and 3.5.

gdb/ChangeLog:

	* python/lib/gdb/printing.py (FlagEnumerationPrinter.__call__):
	Fix enumerators sort key function.

gdb/testsuite/ChangeLog:

	* gdb.python/py-pp-maint.exp: Change/add enum flag tests.
	* gdb.python/py-pp-maint.c (enum flag_enum): Use more complex
	enum flag values.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Detect the arm/thumb mode of code SIGRETURN or RT_SIGRETURN returns to
@ 2016-01-21  8:17 sergiodj+buildbot
  2016-01-21  9:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-21  8:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7a6a40dbc279f0a54bdf947077cbad8ad52564c ***

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

Detect the arm/thumb mode of code SIGRETURN or RT_SIGRETURN returns to

This patch fixes the following regression introduced by commit d0e59a68

step^M
39      } /* handler */^M
1: x/i $pc^M
=> 0x8740 <handler+80>: sub     sp, r11, #0^M
(gdb) step^M
^M
Program received signal SIGSEGV, Segmentation fault.^M
setitimer () at ../sysdeps/unix/syscall-template.S:81^M
81      ../sysdeps/unix/syscall-template.S: No such file or directory.^M
1: x/i $pc^M
=> 0xb6eff9c0 <setitimer>:      push    {r7}^M
(gdb) FAIL: gdb.base/sigstep.exp: continue to handler, si+advance in handler, step from handler: leave handler

in my test setting, program is compiled in arm mode, but the glibc
is built in thumb mode, so when we do 'step' to step over syscall
instruction svc for SIGRETURN, GDB should set breakpoint for arm mode
in the program, even though the current program in glibc is in thumb
mode.  Current GDB doesn't consider the case that the mode of program
SIGRETURN goes to can be different from current program mode.

In fact, GDB has taken care of this arm/thumb mode changes already,
see

/* Copy the value of next pc of sigreturn and rt_sigrturn into PC,
   return 1.  In addition, set IS_THUMB depending on whether we
   will return to ARM or Thumb code.  Return 0 if it is not a
   rt_sigreturn/sigreturn syscall.  */
static int
arm_linux_sigreturn_return_addr (struct frame_info *frame,
				 unsigned long svc_number,
				 CORE_ADDR *pc, int *is_thumb)

but in the commit d0e59a68

> -  arm_linux_sigreturn_return_addr (frame, svc_number, &return_addr, &is_thumb);
> +  if (svc_number == ARM_SIGRETURN || svc_number == ARM_RT_SIGRETURN)
> +    next_pc = arm_linux_sigreturn_next_pc (regcache, svc_number);

the IS_THUMB setting is lost, so it is a regression.

gdb:

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

	* arm-linux-tdep.c (arm_linux_sigreturn_next_pc): Add parameter
	is_thumb and set it according to CPSR saved on the stack.
	(arm_linux_get_next_pcs_syscall_next_pc): Pass is_thumb to
	arm_linux_sigreturn_next_pc.

gdb/gdbserver:

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

	* linux-arm-low.c (arm_sigreturn_next_pc): Add parameter
	is_thumb and set it according to CPSR saved on the stack.
	(get_next_pcs_syscall_next_pc): Pass is_thumb to
	arm_sigreturn_next_pc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] bfd/configure reorganisation
@ 2016-01-21  9:40 sergiodj+buildbot
  2016-01-21 10:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-21  9:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c603b11becccfc593ca590c3129d00c2289359b8 ***

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

bfd/configure reorganisation

Corefile code should be moved after running config.bfd, because it
uses want64.

	* configure.ac: Move corefile selection later in file.  Move
	tdefaults code immediately after other target vector code.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Convert macros in elf-linux-core.h to inline functions
@ 2016-01-21  9:57 sergiodj+buildbot
  2016-01-21 14:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-21  9:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aeb7056972f1b383578204b9151b0ae6d8c1df81 ***

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

Convert macros in elf-linux-core.h to inline functions

Besides changing some macros into inline functions, this removes
redundant memsets and uses bfd_put_* rather than H_PUT_*.

	* elf-linux-core.h (swap_linux_prpsinfo32_out): New function.
	(swap_linux_prpsinfo64_out): New function.
	(LINUX_PRPSINFO32_SWAP_FIELDS): Delete.
	(LINUX_PRPSINFO64_SWAP_FIELDS): Delete.
	* elf.c (elfcore_write_linux_prpsinfo32): Adjust.  Don't memset.
	(elfcore_write_linux_prpsinfo64): Likewise.
	* elf32-ppc.c (swap_ppc_linux_prpsinfo32_out): New function.
	(PPC_LINUX_PRPSINFO32_SWAP_FIELDS): Delete.
	(elfcore_write_ppc_linux_prpsinfo32): Adjust.  Don't memset.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Rename elf-linux-psinfo.h to elf-linux-core.h
@ 2016-01-21 10:09 sergiodj+buildbot
  2016-01-21 12:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 10:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de64ce13a78669f094d6909fce51d210e2f9d2c0 ***

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

Rename elf-linux-psinfo.h to elf-linux-core.h

Since it will sometime have more than just prpsinfo.  Also,
elf32-ppc.c needlessly includes this header.

	* elf-linux-core.h: Rename from elf-linux-psinfo.h.
	* elf.c: Adjust #include.
	* elf32-ppc.c: Don't #include elf-linux-psinfo.h
	* Makefile.am (SOURCE_HFILES): Update.
	* Makefile.in: Regenerate.
	* po/SRC-PORFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Relax long branch veneer insertion for non STT_FUNC symbol
@ 2016-01-21 10:14 sergiodj+buildbot
  2016-01-21 15:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 10:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f340668a9a7c00f8813b097b157b07fba8cfa82 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 2f340668a9a7c00f8813b097b157b07fba8cfa82

[AArch64] Relax long branch veneer insertion for non STT_FUNC symbol

  As defined at AArch64 ELF Specification (4.6.7 Call and Jump
  relocations), symbol with type of non STT_FUNC but in different input
  section with relocation place should insert long branch veneer also.

  Meanwhile the current long branch veneer infrastructure havn't considered
  the situation where the branch destination is "sym_value + rela->addend".

  This was OK because we only insert veneer for long call destination is
  STT_FUNC symbol for which the addend is always zero. But as we relax the
  support to other situations by this patch, we need to handle addend be
  non-zero value. For example, for static function, relocation against
  "local symbol" are turned into relocation against "section symbol + offset"
  where there is a valid addend.

  bfd/
	* elfnn-aarch64.c (aarch64_type_of_stub): Allow insert long branch
	veneer for sym_sec != input_sec.
	(elfNN_aarch64_size_stub): Support STT_SECTION symbol.
	(elfNN_aarch64_final_link_relocate): Take rela addend into account when
	calculation destination.

  ld/
	* testsuite/ld-aarch64/farcall-section.d: Delete.
	* testsuite/ld-aarch64/farcall-section.s: Delete.
	* testsuite/ld-aarch64/farcall-b-section.d: New expectation file.
	* testsuite/ld-aarch64/farcall-bl-section.d: Likewise.
	* testsuite/ld-aarch64/farcall-b-section.s: New testcase.
	* testsuite/ld-aarch64/farcall-bl-section.s: Likewise.
	* testsuite/ld-aarch64/aarch64-elf.exp: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix regression introduced in "break *<EXPR>" by explicit location patches.
@ 2016-01-21 10:33 sergiodj+buildbot
  2016-01-21 16:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 10:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 305e13e67faaf940ce6eb708847a655a0735a651 ***

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

Fix regression introduced in "break *<EXPR>" by explicit location patches.

A relatively recent patch support for explicit locations, and part
of that patch cleaned up the way we parse breakpoint locations.
Unfortunatly, a small regression crept in for "*<EXPR>" breakpoint
locations. In particular, on PIE programs, one can see the issue by
doing the following, with any program:

    (gdb) b *main
    Breakpoint 1 at 0x51a: file hello.c, line 3.
    (gdb) run
    Starting program: /[...]/hello
    Error in re-setting breakpoint 1: Warning:
    Cannot insert breakpoint 1.
    Cannot access memory at address 0x51a

    Warning:
    Cannot insert breakpoint 1.
    Cannot access memory at address 0x51a

Just for the record, this regression was introduced by:

    commit a06efdd6effd149a1d392df8d62824e44872003a
    Date:   Tue Aug 11 17:09:35 2015 -0700
    Subject: Explicit locations: introduce address locations

What happens is that the patch makes the implicit assumption that
the address computed the first time is static, as if it was designed
to only support litteral expressions (Eg. "*0x1234"). This allows
the shortcut of not re-computing the breakpoint location's address
when re-setting breakpoints.

However, this does not work in general, as demonstrated in the example
above.

This patch plugs that hole simply by saving the original expression
used to compute the address as part of the address location, so as
to then re-evaluate that expression during breakpoint re-set.

gdb/ChangeLog:

        * location.h (new_address_location): Add new parameters
        "addr_string" and "addr_string_len".
        (get_address_string_location): Add declaration.
        * location.c (new_address_location): Add new parameters
        "addr_string" and "addr_string_len".  If not NULL, store
        a copy of the addr_string in the new location as well.
        (get_address_string_location): New function.
        (string_to_event_location): Update call to new_address_location.
        * linespec.c (event_location_to_sals) <ADDRESS_LOCATION>:
        Save the event location in the parser's state before
        passing it to convert_address_location_to_sals.
        * breakpoint.c (create_thread_event_breakpoint): Update call
        to new_address_location.
        (init_breakpoint_sal): Get the event location's string, if any,
        and use it to update call to new_address_location.
        * python/py-finishbreakpoint.c (bpfinishpy_init):
        Update call to new_address_location.
        * spu-tdep.c (spu_catch_start): Likewise.

        * config/djgpp/fnchange.lst: Add entries for
        gdb/testsuite/gdb.base/break-fun-addr1.c and
        gdb/testsuite/gdb.base/break-fun-addr2.c.

gdb/testsuite/ChangeLog:

        * gdb.base/break-fun-addr.exp: New file.
        * gdb.base/break-fun-addr1.c: New file.
        * gdb.base/break-fun-addr2.c: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix unexpected failures in the linker testsuite for ARM VxWorks targets.
@ 2016-01-21 11:03 sergiodj+buildbot
  2016-01-21 18:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 11:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aebf9be7089c1903581740851ae9ae67ffee2f4b ***

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

Fix unexpected failures in the linker testsuite for ARM VxWorks targets.

	PR ld/19455
	* elf32-arm.c (elf32_arm_create_dynamic_sections): Set the ELF
	class of the linker stub bfd.
	(elf32_arm_check_relocs): Skip check for pic format after
	processing a vxWorks R_ARM_ABS12 reloc.
	* elflink.c (bfd_elf_final_link): Check for ELFCLASSNONE when
	reporting a class mismatch.

	* testsuite/ld-arm/vxworks1-lib.dd: Update for current
	disassmebler output.
	* testsuite/ld-arm/vxworks1-lib.rd: Likewise.
	* testsuite/ld-arm/vxworks1.dd: Likewise.
	* testsuite/ld-arm/vxworks1.rd: Likewise.
	* testsuite/ld-arm/vxworks1.ld: Set the output format.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Respect CXXFLAGS when building with C++ compiler
@ 2016-01-21 11:45 sergiodj+buildbot
  2016-01-21 19:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a994041db36c9a6058fe591c7ccd018ed7affc76 ***

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

gdb: Respect CXXFLAGS when building with C++ compiler

Currently, even when built with --enable-build-with-cxx, gdb uses
CFLAGS instead of CXXFLAGS.  This commit fixes it.

CXXFLAGS set in the environment when configure was run is now honored
in the generated gdb/Makefile, and you can also override CXXFLAGS in
the command like at make time, with the usual 'make CXXFLAGS="..."'

Objects built with a C compiler (e.g., gnulib) still honor CFLAGS
instead.

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

	* Makefile.in (COMPILER_CFLAGS): New.
	(CXXFLAGS): Get it from configure.
	(INTERNAL_CFLAGS_BASE, INTERNAL_LDFLAGS): Use COMPILER_CFLAGS
	instead of CFLAGS.
	* build-with-cxx.m4 (GDB_AC_BUILD_WITH_CXX): Set and AC_SUBST
	COMPILER_CFLAGS.
	* configure: Regenerate.

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

	* Makefile.in (COMPILER_CFLAGS, CXXFLAGS): New.
	(INTERNAL_CFLAGS_BASE): Use COMPILER_CFLAGS instead of CFLAGS.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Small cleanup to disasm.c:maybe_add_dis_line_entry
@ 2016-01-21 12:28 sergiodj+buildbot
  2016-01-21 21:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 12:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a099de2e7e5374d633ba0eab4273b6f5c81ba74 ***

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

gdb: Small cleanup to disasm.c:maybe_add_dis_line_entry

Give the function a better name (drop "maybe_") and update the header
comment.

gdb/ChangeLog:

	* disasm.c (maybe_add_dis_line_entry): Rename to...
	(add_dis_line_entry): ...this, and update header comment.
	(do_mixed_source_and_assembly): Now use add_dis_line_entry.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix compile time errors building ARC target on a 32-bit host.
@ 2016-01-21 14:04 sergiodj+buildbot
  2016-01-21 23:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 14:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23a42089156e63bbd2228675e78cdf1ffae63c51 ***

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

Fix compile time errors building ARC target on a 32-bit host.

	* elf32-arc.c (ADD_RELA): Fix compile time warning errors by
	changing the type of _loc to be bfd_byte *.
	(elf_arc_finish_dynamic_symbol): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] * lib/ada.exp (gdb_compile_ada): Fix typo.
@ 2016-01-22  0:30 sergiodj+buildbot
  2016-01-22  1:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-22  0:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f5946a8630ec027d412ee078974f8d92e5ab3a0 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 4f5946a8630ec027d412ee078974f8d92e5ab3a0

* lib/ada.exp (gdb_compile_ada): Fix typo.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <f906b857015513af81f94db8e11b1e334c767def@gdb-build>]
* [binutils-gdb] * breakpoint.c (init_breakpoint_sal): Add comment.
@ 2016-01-22  1:15 sergiodj+buildbot
  2016-01-22  3:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-22  1:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b35a8b2f1f44c6ea48aeb6f7a74de01f6f5016fb ***

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

* breakpoint.c (init_breakpoint_sal): Add comment.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] perror_with_name when failed to fetch/store registers
@ 2016-01-22  9:13 sergiodj+buildbot
  2016-01-22 10:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-22  9:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d86feca31bd9b814fd5317a0ebdbe86fb812a1bd ***

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

[ARM] perror_with_name when failed to fetch/store registers

I see the following test fail on native arm-linux gdb testing...

(gdb) PASS: gdb.base/killed-outside.exp: registers: get pid of inferior
Executing on target: kill -9 2346    (timeout = 300)
spawn kill -9 2346^M
flushregs^M
Register cache flushed.^M
warning: Unable to fetch general registers.^M
PC not available^M
(gdb) PASS: gdb.base/killed-outside.exp: registers: flushregs
info threads^M
  Id   Target Id         Frame ^M
* 1    process 2346 "killed-outside" (gdb) FAIL: gdb.base/killed-outside.exp: registers: info threads (timeout)

since the inferior disappeared, ptrace will fail.  In that case, the
exception should be thrown, so that the caller can handle that.

gdb:

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

	* arm-linux-nat.c (fetch_fpregs): Call perror_with_name
	instead of warning.
	(store_fpregs, fetch_regs, store_regs): Likewise.
	(fetch_wmmx_regs, store_wmmx_regs): Likewise.
	(fetch_vfp_regs, store_vfp_regs): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [testsuite] Unbuffer the output in gdb.base/multi-forks.c
@ 2016-01-22  9:39 sergiodj+buildbot
  2016-01-22 11:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-22  9:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ac78c044471fa65b952c2e5c47dcf4d0ccf9b79 ***

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

[testsuite] Unbuffer the output in gdb.base/multi-forks.c

This patch unbuffer the output of the program so that the test harness
can count the number of "done" from output correctly.

gdb/testsuite:

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

	PR testsuite/19491
	* gdb.base/multi-forks.c: Include
	../lib/unbuffer_output.c
	(main): Call gdb_unbuffer_output.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <99e8eb11cfcdde8cba6755ed4613c3cb079dfaa4@gdb-build>]
* [binutils-gdb] Reword the string description of native FreeBSD ptids.
@ 2016-01-22 17:04 sergiodj+buildbot
  2016-01-22 18:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-22 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2bae2f79b11a87af3dbc2a6ca3c0c4987ecfbba ***

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

Reword the string description of native FreeBSD ptids.

The prior format led to confusing messages when threads were created
or added such as "[New process 14757, LWP 100537]".  The new format
reports this as "[New LWP 100434 of process 15652]".

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_pid_to_str): Adjust string format.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Fix PR threads/19422 regression + Guile regression
@ 2016-01-22 20:50 sergiodj+buildbot
  2016-01-22 22:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-22 20:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31d765d3801c63a66312023181edb3af25c03598 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 31d765d3801c63a66312023181edb3af25c03598

testsuite: Fix PR threads/19422 regression + Guile regression

The PR threads/19422 patchset added a new regression.

Additionally below it there was already a regression if --with-guile (which is
default if Guile is found) was used.

racy case #1:

(xgdb) PASS: gdb.gdb/selftest.exp: Set xgdb_prompt
^M
Thread 1 "xgdb" received signal SIGINT, Interrupt.^M
0x00007ffff583bfdd in poll () from /lib64/libc.so.6^M
(gdb) FAIL: gdb.gdb/selftest.exp: send ^C to child process
signal SIGINT^M
Continuing with signal SIGINT.^M
^C^M
Thread 1 "xgdb" received signal SIGINT, Interrupt.^M
0x00007ffff5779da0 in sigprocmask () from /lib64/libc.so.6^M
(gdb) PASS: gdb.gdb/selftest.exp: send SIGINT signal to child process
backtrace^M
errstring=errstring@entry=0x7e0e6c "", mask=mask@entry=RETURN_MASK_ALL) at exceptions.c:240^M
errstring=errstring@entry=0x7e0e6c "", mask=mask@entry=RETURN_MASK_ALL) at exceptions.c:240^M
(gdb) PASS: gdb.gdb/selftest.exp: backtrace through signal handler

racy case #2:

(xgdb) PASS: gdb.gdb/selftest.exp: Set xgdb_prompt
^M
Thread 1 "xgdb" received signal SIGINT, Interrupt.^M
0x00007ffff583bfdd in poll () from /lib64/libc.so.6^M
(gdb) FAIL: gdb.gdb/selftest.exp: send ^C to child process
signal SIGINT^M
Continuing with signal SIGINT.^M
^C^M
Thread 2 "xgdb" received signal SIGINT, Interrupt.^M
[Switching to Thread 0x7ffff3b7f700 (LWP 13227)]^M
0x00007ffff6b88b10 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0^M
(gdb) PASS: gdb.gdb/selftest.exp: send SIGINT signal to child process
backtrace^M
(gdb) FAIL: gdb.gdb/selftest.exp: backtrace through signal handler

Pedro Alves:
Not all targets support thread names, and even those that do, not all
use the program name as default thread name -- I think that's only true
for GNU/Linux, actually.  So I think it's best to not expect that, like:
            -re "(Thread .*|Program) received signal SIGINT.*$gdb_prompt $" {

gdb/testsuite/ChangeLog
2016-01-22  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Fix testsuite compatibility with Guile.
	* gdb.gdb/selftest.exp (send ^C to child process): Accept also Thread.
	(thread 1): New test for backtrace through signal handler.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: gdb.gdb/selftest.exp: Drop expected Thread number
@ 2016-01-22 21:00 sergiodj+buildbot
  2016-01-22 23:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-22 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 092127d743462e370fd1156cb746f814a7b46593 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 092127d743462e370fd1156cb746f814a7b46593

testsuite: gdb.gdb/selftest.exp: Drop expected Thread number

Pedro Alves:
Looks like you forgot to amend before pushing though -- the version
checked in still had "Thread 1".

gdb/testsuite/ChangeLog
2016-01-22  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	Fix testsuite compatibility with Guile.
	* gdb.gdb/selftest.exp (send ^C to child process): Drop expected Thread
	number.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <cc5fd9abe4980e48e2cc27b0225f3c6ba7c0756b@gdb-build>]
[parent not found: <dc29a1ce6a25233e608f90511e67af3c18e19a98@gdb-build>]
* [binutils-gdb] MIPS/BFD: Correct register index calculation in BZ16_REG
@ 2016-01-24  1:16 sergiodj+buildbot
  2016-01-24  2:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-24  1:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e67f83e590b8ce7a9912f665aa559cbc98c05de6 ***

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

MIPS/BFD: Correct register index calculation in BZ16_REG

For the 3-bit register encodings of { 0, 1, 2, 3, 4, 5, 6, 7 } return
the 5-bit encodings of { 16, 17, 2, 3, 4, 5, 6, 7 } respectively rather
than { 24, 25, 2, 3, 4, 5, 6, 7 }.

	bfd/
	* elfxx-mips.c (BZ16_REG): Correct calculation.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Simplify register index calculation in BZ16_REG_FIELD
@ 2016-01-24  1:27 sergiodj+buildbot
  2016-01-24  3:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-24  1:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb6b0cf45d7588eb147d90ce790254309a69613e ***

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

MIPS/BFD: Simplify register index calculation in BZ16_REG_FIELD

Just mask higher bits off, which returns the same set of 3-bit register
encodings of { 0, 1, 2, 3, 4, 5, 6, 7 } for the allowed 5-bit encodings
of { 16, 17, 2, 3, 4, 5, 6, 7 }.  Input has already been validated with
OP16_VALID_REG.

	bfd/
	* elfxx-mips.c (BZ16_REG_FIELD): Simplify calculation.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix memory corruption on Mach-O systems by suppressing a memory tidy up.
@ 2016-01-25  9:41 sergiodj+buildbot
  2016-01-25  9:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-25  9:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf466c2ac5ac55bb9b30b96fbdcad564e8c1ccc8 ***

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

Fix memory corruption on Mach-O systems by suppressing a memory tidy up.

	PR target/19435
	* mach-o.c (bfd_mach_o_close_and_cleanup): Suppress code to free
	dsym filename buffer.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add missing end-of-comment marker to previous delta. (Doh!)
@ 2016-01-25  9:54 sergiodj+buildbot
  2016-01-25 11:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-25  9:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c244074cb684302be1378a072b33cdb8dd0dff1f ***

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

Add missing end-of-comment marker to previous delta.  (Doh!)


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Move foreach_with_prefix to lib/gdb.exp
@ 2016-01-25 13:32 sergiodj+buildbot
  2016-01-25 14:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f1da4b11eef6dba04a1cfa579c6ba313718105b8 ***

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

Move foreach_with_prefix to lib/gdb.exp

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

	* gdb.base/step-sw-breakpoint-adjust-pc.exp (foreach_with_prefix):
	Delete, moved to lib/gdb.exp.
	* gdb.threads/forking-threads-plus-breakpoint.exp
	(foreach_with_prefix): Likewise.
	* gdb.threads/process-dies-while-handling-bp.exp
	(foreach_with_prefix): Likewise.
	* lib/gdb.exp (foreach_with_prefix): New procedure.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <45f3854667c659ab053f51f96e1923f36e6e20ba@gdb-build>]
* [binutils-gdb] Fix PR 19494: hang when killing unfollowed fork children
@ 2016-01-25 13:40 sergiodj+buildbot
  2016-01-25 16:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 13:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d2736d43ba16c585e643faec4b6a5084d782289 ***

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

Fix PR 19494: hang when killing unfollowed fork children

linux_nat_kill relies on get_last_target_status to determine whether
the current inferior is stopped at a unfollowed fork/vfork event.
This is bad because many things can happen ever since we caught the
fork/vfork event...  This commit rewrites that code to instead walk
the thread list looking for unfollowed fork events, similarly to what
was done for remote.c.

New test included.  The main idea of the test is make sure that when
the program stops for a fork catchpoint, and the user kills the
parent, gdb also kills the unfollowed fork child.  Since the child
hasn't been added as an inferior at that point, we need some other
portable way to detect that the child is gone.  The test uses a pipe
for that.  The program forks twice, so you have grandparent, child and
grandchild.  The grandchild inherits the write side of the pipe.  The
grandparent hangs reading from the pipe, since nothing ever writes to
it.  If, when GDB kills the child, it also kills the grandchild, then
the grandparent's pipe read returns 0/EOF and the test passes.
Otherwise, if GDB doesn't kill the grandchild, then the pipe read
never returns and the test times out, like:

 FAIL: gdb.base/catch-fork-kill.exp: fork-kind=fork: exit-kind=kill: fork: kill parent (timeout)
 FAIL: gdb.base/catch-fork-kill.exp: fork-kind=vfork: exit-kind=kill: vfork: kill parent (timeout)

No regressions on x86_64 Fedora 20.  New test passes with gdbserver as
well.

gdb/ChangeLog:
2016-01-25  Pedro Alves  <palves@redhat.com>

	PR gdb/19494
	* linux-nat.c (kill_one_lwp): New, factored out from ...
	(kill_callback): ... this.
	(kill_wait_callback): New, factored out from ...
	(kill_wait_one_lwp): ... this.
	(kill_unfollowed_fork_children): New function.
	(linux_nat_kill): Use it.

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

	PR gdb/19494
	* gdb.base/catch-fork-kill.c: New file.
	* gdb.base/catch-fork-kill.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR 19461: strange "info thread" behavior in non-stop
@ 2016-01-25 13:48 sergiodj+buildbot
  2016-01-25 17:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 13:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2077e254098828614ef6621cf8df28185e711d0 ***

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

Fix PR 19461: strange "info thread" behavior in non-stop

If you have "set follow-fork child" set, then if you do "info threads"
right after a fork, and before the child reports any other event to
GDB core, you'll see:

(gdb) info threads
  Id   Target Id         Frame
* 1.1  Thread 0x7ffff7fc1740 (LWP 31875) "fork-plus-threa" (running)
  2.1  process 31879 "fork-plus-threa" Selected thread is running.
(gdb)

The "Selected thread is running." bit is a bogus error.  That was GDB
trying to fetch the current frame of thread 2.1, because the external
runnning state is "stopped", and then throwing an error because the
thread is actually running.

This actually affects all-stop + schedule-multiple as well.

The problem here is that on a fork event, GDB doesn't update the
external parent/child running states.

New comprehensive test included.  The "kill inferior 1" / "kill
inferior 2" bits also trip on PR gdb/19494 (hang killing unfollowed
fork children), which was fixed by the previous patch.

gdb/ChangeLog:
2016-01-25  Pedro Alves  <palves@redhat.com>

	PR threads/19461
	* infrun.c (handle_inferior_event_1) <fork/vfork>: Update
	parent/child running states.

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

	PR threads/19461
	* gdb.base/fork-running-state.c: New file.
	* gdb.base/fork-running-state.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [PATCH[ARM]Check mapping symbol while backward searching for IT block.
@ 2016-01-25 15:24 sergiodj+buildbot
  2016-01-25 18:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 15:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5bc5ae8810c03b55f46b9e575389c3fa85a62b5c ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 5bc5ae8810c03b55f46b9e575389c3fa85a62b5c

[PATCH[ARM]Check mapping symbol while backward searching for IT block.

opcodes/

	* arm-dis.c (mapping_symbol_for_insn): New function.
	(find_ifthen_state): Call mapping_symbol_for_insn().

gas/

	* testsuite/gas/arm/thumb2_it_search.d: New.
	* testsuite/gas/arm/thumb2_it_search.s: New.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] ARC/BFD: Fix a build error from `index' shadowing a global declaration
@ 2016-01-25 16:18 sergiodj+buildbot
  2016-01-25 20:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 16:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 840855c5edfb840a97fb063fd8f44a7e9e537b87 ***

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

ARC/BFD: Fix a build error from `index' shadowing a global declaration

	bfd/
	* elf32-arc.c (elf_arc_finish_dynamic_symbol): Rename `index' to
	`dynindx'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove new_thread_notify and dead_thread_notify
@ 2016-01-25 16:27 sergiodj+buildbot
  2016-01-25 21:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 16:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0f8e08a3c357ae24d3244940e1c6b405a0c17cc ***

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

Remove new_thread_notify and dead_thread_notify

They were added by

  PATCH: Multithreaded debugging for gdbserver
  https://sourceware.org/ml/gdb-patches/2002-06/msg00157.html

but as a no-op, and the last usage of them was removed by

  [gdbserver/RFC/RFA] Implement multiprocess extensions, add linux multiproces support.
  https://sourceware.org/ml/gdb-patches/2009-03/msg00667.html

This patch is to remove them.

gdb/gdbserver:

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

	* remote-utils.c (new_thread_notify): Remove.
	(dead_thread_notify): Likewise.
	* remote-utils.h (new_thread_notify): Remove declaration.
	(dead_thread_notify): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <a579cd9aa8c57c8a54833f26452a1afef38e5d20@gdb-build>]
* [binutils-gdb] [GDBserver] Check input interrupt after reading in a packet
@ 2016-01-26 14:03 sergiodj+buildbot
  2016-01-26 15:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 14:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18879fef1741464e522624bcc529048400453e0d ***

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

[GDBserver] Check input interrupt after reading in a packet

GDBserver may read some packet together with '\003' in one go.  We've
already checked '\003' first when reading packet by my patch,

  Check input interrupt first when reading packet
  https://sourceware.org/ml/gdb-patches/2016-01/msg00057.html

but if we don't check '\003' *after* each packet, the interrupt will
be processed next time GDBserver reads from the buffer, so that the
interrupt isn't processed in time.  For example, GDB sends vCont;c and
interrupt (see gdb.base/interrupt-noterm.exp), we'll resume the
inferior and wait once packet vCont;c is seen.  If we don't check the
interrupt character after vCont;c packet, interrupt character will stay
in the buffer unattended until GDBserver returns from the wait, which
may take a while.  Note that since we've read '\003' from file
descriptor, SIGIO signal handler input_interrupt doesn't help either.

This issue can be exposed by hacking the end of getpkt like
@@ -1041,6 +1050,9 @@ getpkt (char *buf)
        }
     }

+  if (readchar_bufcnt > 0)
+    gdb_assert (*readchar_bufp != '\003');
+
   return bp - buf;
 }

and this can trigger internal error,
(gdb) PASS: gdb.base/interrupt-noterm.exp: interrupt
Remote connection closed^M
(gdb) FAIL: gdb.base/interrupt-noterm.exp: inferior received SIGINT
Remote debugging from host 10.2.206.40^M
/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/remote-utils.c:1054: A problem internal to GDBserver has been detected.^M
getpkt: Assertion `*readchar_bufp != '\003'' failed.^M

This patch is to peek the buffer, if it is '\003', consume it and call
*the_target->request_interrupt.

gdb/gdbserver:

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

	* remote-utils.c (getpkt): If the buffer isn't empty, and the
	first character is '\003', call *the_target->request_interrupt.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove argument pc in get_next_pcs
@ 2016-01-26 14:48 sergiodj+buildbot
  2016-01-26 21:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 14:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d18591be953e2faeaaa280484d375fe05857770 ***

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

Remove argument pc in get_next_pcs

Nowadays, get_next_pcs in linux_target_ops has two parameters PC
and REGCACHE.  Parameter PC looks redundant because it can be go
from REGCACHE.  The patch is to remove PC from the arguments for
various functions.

gdb:

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

	* arch/arm-get-next-pcs.c (thumb_deal_with_atomic_sequence_raw):
	Remove argument pc.  Get pc by regcache_read_pc.  Callers updated.
	(arm_deal_with_atomic_sequence_raw): Likewise.
	(thumb_get_next_pcs_raw): Likewise.
	(arm_get_next_pcs_raw): Likewise.
	(arm_get_next_pcs): Remove argument pc.  Callers updated.
	* arch/arm-get-next-pcs.h (arm_get_next_pcs): Update declaration.

gdb/gdbserver:

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

	* linux-arm-low.c (arm_gdbserver_get_next_pcs): Remove argument pc.
	* linux-low.c (install_software_single_step_breakpoints): Don't
	call regcache_read_pc.
	* linux-low.h (struct linux_target_ops) <get_next_pcs>: Remove
	argument pc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix function comments
@ 2016-01-26 21:41 sergiodj+buildbot
  2016-01-26 23:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 21:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41548caa9b7ffba43e856bd288b98cc1ab8c3e8f ***

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

Fix function comments

Two obvious fixes.

gdb/ChangeLog:

	* common/common-utils.c (skip_spaces): Fix comment.
	(skip_to_space_const): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add Keith Seitz as Linespec Maintainer
@ 2016-01-27 11:38 sergiodj+buildbot
  2016-01-27 13:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-27 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c07af0ab296efebf868a153e6c98cb65c5c23d04 ***

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

Add Keith Seitz as Linespec Maintainer

gdb/ChangeLog:

        * MAINTAINERS (Responsible Maintainers): Add Keith Seitz as
        Linespec Maintainers.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Import strchrnul from gnulib and use it
@ 2016-01-28 15:47 sergiodj+buildbot
  2016-01-28 19:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 15:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8424cc978c8c76aca7945d50408762de65646095 ***

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

Import strchrnul from gnulib and use it

For a forthcoming patch, I need a "skip_to_colon" function.  I noticed
there are two skip_to_semicolon (one in gdb and one in gdbserver). I
thought we could put it in common/, and generalize it for any character.
It turns out that the strchrnul function does exactly that.  I imported
the corresponding module from gnulib, for those systems that do not have
it.

There are probably more places where this function can be used instead
of doing the work by hand (I am looking at
remote-utils.c::look_up_one_symbol).

gdb/ChangeLog:

	* remote.c (skip_to_semicolon): Remove.
	(remote_parse_stop_reply): Use strchrnul instead of
	skip_to_semicolon.
	* gnulib/update-gnulib.sh (IMPORTED_GNULIB_MODULES): Add
	strchrnul.
	* gnulib/aclocal.m4: Regenerate.
	* gnulib/config.in: Regenerate.
	* gnulib/configure: Regenerate.
	* gnulib/import/Makefile.am: Regenerate.
	* gnulib/import/Makefile.in: Regenerate.
	* gnulib/import/m4/gnulib-cache.m4: Regenerate.
	* gnulib/import/m4/gnulib-comp.m4: Regenerate.
	* gnulib/import/m4/rawmemchr.m4: New file.
	* gnulib/import/m4/strchrnul.m4: New file.
	* gnulib/import/rawmemchr.c: New file.
	* gnulib/import/rawmemchr.valgrind: New file.
	* gnulib/import/strchrnul.c: New file.
	* gnulib/import/strchrnul.valgrind: New file.

gdb/gdbserver/ChangeLog:

	* server.c (skip_to_semicolon):  Remove.
	(process_point_options): Use strchrnul instead of
	skip_to_semicolon.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Sync libiberty with GCC.
@ 2016-01-28 21:00 sergiodj+buildbot
  2016-01-28 22:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d98de835cb018419e0ef97db37fcf9061247750 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 9d98de835cb018419e0ef97db37fcf9061247750

Sync libiberty with GCC.

libiberty/ChangeLog:
	* d-demangle.c (dlang_call_convention): Handle extern Objective-C
	function calling convention.
	(dlang_call_convention_p): Likewise.
	(dlang_type): Likewise.
	* testsuite/d-demangle-expected: Add coverage tests.

	* d-demangle.c (dlang_function_args): Append ',' for variadic functions
	only if parameters were seen before the elipsis symbol.
	* testsuite/d-demangle-expected: Add coverage test for parameter-less
	variadic functions.

	* d-demangle.c (dlang_type): Handle function types only in the context
	of seeing a pointer type symbol.
	* testsuite/d-demangle-expected: Update function pointer tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix two misleading indentation warnings
@ 2016-01-29 20:45 sergiodj+buildbot
  2016-01-29 22:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-29 20:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2e3e93f4423899d99687da3ce4ac57cbed437f9 ***

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

Fix two misleading indentation warnings

Two small changes so everything builds with latest GCC and its
-Wmisleading-indentation.

In the aarch64-tdep.c case, the two misindented lines should actually be
part of the for loop.  It looks like the indentation is all done using
spaces in that file though...  I fixed it (changed for tabs + spaces) for
the lines I touched.

In the xcoffread.c case, we can simply remove the braces and fix the
indentation.

gdb/ChangeLog:

	* aarch64-tdep.c (aarch64_record_asimd_load_store): Add braces
	to for include additional lines.
	* xcoffread.c (scan_xcoff_symtab): Remove unnecessary braces.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix /usr/bin/ld: final link failed: File truncated error on hppa.
@ 2016-01-31 20:38 sergiodj+buildbot
  2016-01-31 22:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-01-31 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d4b2867f8441c7bf75dfef6b3c95a10241f9709 ***

Author: John David Anglin <danglin@gcc.gnu.org>
Branch: master
Commit: 6d4b2867f8441c7bf75dfef6b3c95a10241f9709

Fix /usr/bin/ld: final link failed: File truncated error on hppa.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] elf64-s390.c: Fix -Werror=misleading-indentation
@ 2016-02-01  3:01 sergiodj+buildbot
  2016-02-01  4:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-01  3:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bc7245a3a6da700ed13bace22cdc157dc80f58d ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 0bc7245a3a6da700ed13bace22cdc157dc80f58d

elf64-s390.c: Fix -Werror=misleading-indentation

../../bfd/elf64-s390.c: In function 'elf_s390_reloc_name_lookup':
../../bfd/elf64-s390.c:340:5: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation]
     if (strcasecmp (elf64_s390_vtinherit_howto.name, r_name) == 0)
     ^~
../../bfd/elf64-s390.c:333:3: note: ...this 'for' clause, but it is not
   for (i = 0;
   ^~~

bfd/
	* elf64-s390.c (elf_s390_reloc_name_lookup): Fix indentation.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix some comments in varobj.{c,h}
@ 2016-02-01  3:36 sergiodj+buildbot
  2016-02-01  6:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-01  3:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fa1307022c1278575846faba5f3391b70d64b16 ***

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

Fix some comments in varobj.{c,h}

A few typos.  The comment about varobj_create has been misplaced since
the dawn of time.

gdb/ChangeLog:

	* varobj.h (struct varobj): Fix typos in comments.
	(struct lang_varobj_ops): Likewise.
	* varobj.c (VAROBJ_TABLE_SIZE): Likewise.
	(varobj_create): Move misplaced comment.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for importing data from ILF images.
@ 2016-02-01 13:53 sergiodj+buildbot
  2016-02-01 17:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 13:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 655ed9ea1703173cb796070ed9843ea90bb74e58 ***

Author: Nathaniel Smith <njs@pobox.com>
Branch: master
Commit: 655ed9ea1703173cb796070ed9843ea90bb74e58

Add support for importing data from ILF images.

	* peicode.h (pe_ILF_build_a_bfd): Create an import symbol for both
	CODE and DATA.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: New set/show max-value-size command.
@ 2016-02-01 18:23 sergiodj+buildbot
  2016-02-01 19:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 18:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fdf6324fafd60f967e2e8323fdacf84b1bfcea3 ***

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

gdb: New set/show max-value-size command.

For languages with dynamic types, an incorrect program, or uninitialised
variables within a program, could result in an incorrect, overly large
type being associated with a value.  Currently, attempting to print such
a variable will result in gdb trying to allocate an overly large buffer.

If this large memory allocation fails then the result can be gdb either
terminating, or (due to memory contention) becoming unresponsive for the
user.

A new user visible variable in gdb helps guard against such problems,
two new commands are available:

   set max-value-size
   show max-value-size

The 'max-value-size' is the maximum size of memory in bytes that gdb
will allocate for the contents of a value.  Any attempt to allocate a
value with a size greater than this will result in an error.  The
initial default for this limit is set at 64k, this is based on a similar
limit that exists within the ada specific code.

It is possible for the user to set max-value-size to unlimited, in which
case the old behaviour is restored.

gdb/ChangeLog:

	* value.c (max_value_size): New variable.
	(MIN_VALUE_FOR_MAX_VALUE_SIZE): New define.
	(show_max_value_size): New function.
	(check_type_length_before_alloc): New function.
	(allocate_value_contents): Call check_type_length_before_alloc.
	(set_value_enclosing_type): Likewise.
	(_initialize_values): Add set/show handler for max-value-size.
	* NEWS: Mention new set/show command.

gdb/doc/ChangeLog:

	* gdb.texinfo (Value Sizes): New section.
	(Data): Add the 'Value Sizes' node to the menu.

gdb/testsuite/ChangeLog:

	* gdb.base/max-value-size.c: New file.
	* gdb.base/max-value-size.exp: New file.
	* gdb.base/huge.exp: Disable max-value-size for this test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Test gdb.threads/forking-threads-plus-breakpoint.exp with displaced stepping off
@ 2016-02-01 19:35 sergiodj+buildbot
  2016-02-01 23:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 19:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b2e4f10aeb64868720de06d3b2da3cc2d908f10 ***

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

Test gdb.threads/forking-threads-plus-breakpoint.exp with displaced stepping off

This exposes the internal error Don mentioned in PR19496:

  (1) internal error --  gdb/target.c:2713: internal-error: Can't determine the current address space of thread

More analysis here:

  https://sourceware.org/ml/gdb-patches/2016-01/msg00685.html

The (now kfailed) internal error looks like:

 continue &
 Continuing.
 (gdb) PASS: gdb.threads/forking-threads-plus-breakpoint.exp: cond_bp_target=1: detach_on_fork=on: displaced=off: continue &
 [New Thread 2846.2847]
 (...)
 [New Thread 2867.2867]
 /home/pedro/gdb/mygit/src/gdb/target.c:2723: internal-error: Can't determine the current address space of thread Thread 2846.2846

 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n) KFAIL: gdb.threads/forking-threads-plus-breakpoint.exp: cond_bp_target=1: detach_on_fork=on: displaced=off: inferior 1 exited (GDB internal error) (PRMS: remote/19496)
 Resyncing due to internal error.

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

	PR remote/19496
	* gdb.threads/forking-threads-plus-breakpoint.exp
	(displaced_stepping_supported): New global.
	(probe_displaced_stepping_support): New procedure.
	(do_test): Add 'displaced' parameter, and use it.
	(top level): Check for displaced stepping support.  Add displaced
	stepping on/off testing axis.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb.base/skip.exp: Clean up multiple references to same test name.
@ 2016-02-01 23:33 sergiodj+buildbot
  2016-02-02  1:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 23:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9482b9fbb6414468228c618c165e397116a4a8f8 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 9482b9fbb6414468228c618c165e397116a4a8f8

gdb.base/skip.exp: Clean up multiple references to same test name.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't add DT_NEEDED for unmatched symbol
@ 2016-02-01 23:59 sergiodj+buildbot
  2016-02-02  3:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 23:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aef28989904e92e391fee905e51abc6bb2fd4de0 ***

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

Don't add DT_NEEDED for unmatched symbol

Don't add DT_NEEDED if a symbol from a library loaded via DT_NEEDED
doesn't match the symbol referenced by regular object.

bfd/

	PR ld/19553
	* elflink.c (elf_link_add_object_symbols): Don't add DT_NEEDED
	if a symbol from a library loaded via DT_NEEDED doesn't match
	the symbol referenced by regular object.

ld/testsuite/

	PR ld/19553
	* testsuite/ld-elf/indirect.exp: Run tests for PR ld/19553.
	* testsuite/ld-elf/pr19553.map: New file.
	* testsuite/ld-elf/pr19553.map: Likewise.
	* testsuite/ld-elf/pr19553a.c: Likewise.
	* testsuite/ld-elf/pr19553b.c: Likewise.
	* testsuite/ld-elf/pr19553b.out: Likewise.
	* testsuite/ld-elf/pr19553c.c: Likewise.
	* testsuite/ld-elf/pr19553c.out: Likewise.
	* testsuite/ld-elf/pr19553d.c: Likewise.
	* testsuite/ld-elf/pr19553d.out: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Preparation for new siginfo on Linux
@ 2016-02-02 11:05 sergiodj+buildbot
  2016-02-02 14:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 11:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43564574f1de367f537a37bf6ec83bb4c29627c6 ***

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

Preparation for new siginfo on Linux

First add new structure and function to allow architecture customization
for the siginfo structure.

2016-01-15  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* linux-tdep.h (linux_siginfo_extra_field_values): New enum values.
	(linux_siginfo_extra_fields): New enum type.
	* linux-tdep.c (linux_get_siginfo_type_with_fields): New function.
	(linux_get_siginfo_type): Use new function.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] epiphany/disassembler: Improve alignment of output.
@ 2016-02-02 11:38 sergiodj+buildbot
  2016-02-02 20:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b89807c67baf4f31125d151f2dc3532b3420964d ***

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

epiphany/disassembler: Improve alignment of output.

Always set the bytes_per_line field (of struct disassemble_info) to the
same constant value, this is inline with the advice contained within
include/dis-asm.h.

Setting this field to a constant value will cause the disassembler
output to be better aligned.

cpu/ChangeLog:

	* epiphany.opc (epiphany_print_insn): Set info->bytes_per_line to
	a constant to better align disassembler output.

opcodes/ChangeLog:

	* epiphany-dis.c: Regenerated from latest cpu files.

gas/ChangeLog:

	* testsuite/gas/epiphany/sample.d: Update expected output.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Adaptation of siginfo fixup for the new bnd fields
@ 2016-02-02 12:26 sergiodj+buildbot
  2016-02-02 19:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f2f6cb5e8922b680de9d67ad83d3b571d3b2a46 ***

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

Adaptation of siginfo fixup for the new bnd fields

New bnds fields will be always present for x86 architecture.
Fixup for compatibility layer 32bits has to be fixed.

It was added the nat_siginfo to serving as intermediate step
between kernel provided siginfo and the fix up routine.

When executing compat_siginfo_from_siginfo or
compat_x32_siginfo_from_siginfo first the buffer read from the kernel are
converted into the nat_signfo for homogenization, then the fields of
nat_siginfo are use to set the compat and compat_x32 siginfo fields.

In other to make this conversion independent of the system where gdb
is compiled the most complete version of the siginfo, named as native
siginfo, is used internally as an intermediate step.

Conversion using nat_siginfo is exemplified below:

compat_siginfo_from_siginfo or compat_x32_siginfo_from_siginfo:

buffer (from the kernel) -> nat_siginfo -> 32 / X32 siginfo
                      (memcpy)       (field by field)

siginfo_from_compat_x32_siginfo or siginfo_from_compat_siginfo:

32 / X32 siginfo -> nat_siginfo -> buffer (to the kernel)
          (field by field)    (memcpy)

Caveat: No support for MPX on x32.

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

gdb/ChangeLog:

	* amd64-linux-siginfo.c (nat_siginfo_t, nat_sigval_t, nat_timeval):
	New types.
	(compat_siginfo): New bound fields added.
	(compat_x32_siginfo): New field added.
	(cpt_si_addr_lsb): New define.
	(compat_siginfo_from_siginfo): Use nat_siginfo.
	(siginfo_from_compat_siginfo): Use nat_siginfo.
	(compat_x32_siginfo_from_siginfo): Likewise.
	(siginfo_from_compat_x32_siginfo): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Clear HAS_RELOC if there are no relocations
@ 2016-02-02 12:31 sergiodj+buildbot
  2016-02-03  0:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 12:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14f2c699ddca1e2f706342dffc59a6c7e23e844c ***

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

Clear HAS_RELOC if there are no relocations

The HAS_RELOC bit should be cleared when relocations are removed from
relocatable files.

bfd/

	PR binutils/19547
	* elf.c (assign_section_numbers): Clear HAS_RELOC if there are
	no relocations in relocatable files.

binutils/

	PR binutils/19547
	* testsuite/binutils-all/objcopy.exp
	(objcopy_test_without_global_symbol): New proc.
	Run objcopy_test_without_global_symbol.
	* testsuite/binutils-all/pr19547.c: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PowerPC64 ELFv2 entry code
@ 2016-02-02 13:44 sergiodj+buildbot
  2016-02-03  1:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 85fabe715c441e1c90fe913e2a6d65f0e487e5e8 ***

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

PowerPC64 ELFv2 entry code

This tightens the condition under which ld optimizes PIC entry code
to non-PIC.

bfd/
	* elf64-ppc.c (ppc64_elf_relocate_section): Further restrict
	ELFv2 entry optimization.
gold/
	* powerpc.cc (relocate): Further restrict ELFv2 entry optimization.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix typos in bfd/ChangeLog and bfd/elf64-x86-64.c
@ 2016-02-02 21:21 sergiodj+buildbot
  2016-02-03  5:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 21:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb06f1c0f25d27006b28a94e54273a6bb35b5926 ***

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

Fix typos in bfd/ChangeLog and bfd/elf64-x86-64.c


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: mips: fix prog_bfd usage
@ 2016-02-06  1:39 sergiodj+buildbot
  2016-02-06  3:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-06  1:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1554f758410c4307103120424d35050e88433d85 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1554f758410c4307103120424d35050e88433d85

sim: mips: fix prog_bfd usage

We do not want to reference the "base" member directly.  We have the
STATE_PROG_BFD macro instead to look up the prog_bfd member.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] varobj: Cleanup dead code
@ 2016-02-07 14:56 sergiodj+buildbot
  2016-02-07 16:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-07 14:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30914ca8c030eedc4a7e1f1acc878211639cc1ca ***

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

varobj: Cleanup dead code

This patch removes some dead code.

I noticed that varobj_delete was always called with dellist == NULL, so
I started removing that parameter.  That allows removing a good chunk of
the code in varobj_delete, making it almost trivial.  We can also remove
the resultp parameters in that whole trail.  In turn, this shows that
struct cpstack, cppush and cppop were only used fo that mechanism, so
they can be removed as well.

I also moved the function comment to the header file to comply with
today's guideline, even though the rest of the file does not respect it
(yet).

gdb/ChangeLog:

	* varobj.h (varobj_delete): Remove dellist parameter, update and
	move documentation here.
	* varobj.c (struct cpstack, cppush, cppop): Remove.
	(delete_variable): Remove resultp (first) parameter.
	(delete_variable_1): Likewise.
	(varobj_delete): Remove dellist parameter and unused code.
	(update_dynamic_varobj_children): Adjust varobj_delete call.
	(update_type_if_necessary): Likewise.
	(varobj_set_visualizer): Likewise.
	(varobj_update): Likewise.
	(value_of_root): Likewise.
	(varobj_invalidate_iter): Likewise.
	* mi/mi-cmd-var.c (mi_cmd_var_delete): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] remote.c: Cleanup unused variables
@ 2016-02-08 18:12 sergiodj+buildbot
  2016-02-08 19:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-08 18:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5488790363bf8f338e7aec4731f8bed472a2fcf9 ***

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

remote.c: Cleanup unused variables

I built remote.c with -Wunused, to check a function I was working on,
turns out there is a bunch of unused variables.

gdb/ChangeLog:

	* remote.c (remote_register_number_and_offset): Remove unused
	variable(s).
	(remote_thread_always_alive): Likewise.
	(remote_update_thread_list): Likewise.
	(process_initial_stop_replies): Likewise.
	(remote_start_remote): Likewise.
	(remote_check_symbols): Likewise.
	(discard_pending_stop_replies): Likewise.
	(process_stop_reply): Likewise.
	(putpkt_binary): Likewise.
	(getpkt): Likewise.
	(remote_add_target_side_condition): Likewise.
	(remote_insert_breakpoint): Likewise.
	(remote_supports_stopped_by_sw_breakpoint): Likewise.
	(remote_supports_stopped_by_hw_breakpoint): Likewise.
	(remote_xfer_partial): Likewise.
	(remote_read_btrace): Likewise.
	(remote_async_serial_handler): Likewise.
	(remote_thread_events): Likewise.
	(_initialize_remote): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix in-tree, parallel running of Ada tests
@ 2016-02-08 19:12 sergiodj+buildbot
  2016-02-08 21:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-08 19:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 437277d47a15711f29e02e5265ce8bbb8c8ef4f5 ***

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

Fix in-tree, parallel running of Ada tests

While testing the following patch,

  [PATCH] Always organize test artifacts in a directory hierarchy
  https://sourceware.org/ml/gdb-patches/2016-01/msg00133.html

I noticed that it broke Ada testing.  This lead me to think that
parallel testing when building in-tree didn't work previously in Ada.
It is confirmed by this test:

$ make check TESTS="gdb.ada/fun_addr.exp" -j 2
...
Running ./gdb.ada/fun_addr.exp ...
FAIL: gdb.ada/fun_addr.exp: compilation foo.adb
...

This patch fixes in-tree parallel testing for Ada, and consequently
serial and parallel testing when the aforementioned patch is applied.

The problem originates from the fact that Ada support code cd's to the
builddir before compiling.  In itself it's not a problem, it allows to
place intermediate auto-generated files in that directory.  The Ada
compilation refers to the source file, which is in another directory,
only by its base name (e.g. foo.adb).  In serial mode, that worked
because builddir was the same as the source directory (e.g.
gdb.ada/fun_addr/).  In an out-of-tree build, it works because the
source directory is added as an include directory (note: this is not the
same $srcdir as autoconf's):

  set srcdir [file dirname $source]
  additional_flags=-I$srcdir

which becomes:

  additional_flags=-I/home/emaisin/build/binutils-gdb/gdb/testsuite/gdb.ada/fun_addr

However, when building in-tree, srcdir is relative: ./gdb.ada/fun_addr.
When using parallel or always-in-outputs-directory mode, we are cd'ed in
the outputs directory.  So -I$srcdir is relative to the current
directory, which is wrong.

To fix it, I made the TCL variable srcdir (set in site.exp, from which
everything else is derived) always absolute.  It is done by assigning
autoconf's abs_srcdir instead of autoconf's srcdir.  This way -I$srcdir
will always be good, regardless of where we cd'ed to.  A small apparent
change is that when running tests, DejaGnu will say:

  Running /tmp/binutils-gdb/gdb/testsuite/gdb.ada/fun_addr.exp ...

instead of

  Running ./gdb.ada/fun_addr.exp ...

I hope it's not too much of an annoyance.  I think that it should make
the testsuite a tiny bit more robust against other bugs of the same
class.

Regtested in & out of tree, only with native target.

gdb/testsuite/ChangeLog:

	* Makefile.in (abs_srcdir): Assign @abs_srcdir@.
	(site.exp): Assign abs_srcdir to tcl's srcdir.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Always organize test artifacts in a directory hierarchy
@ 2016-02-08 19:40 sergiodj+buildbot
  2016-02-08 23:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-08 19:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2151ccc56c74b55a8f0debf0724a495368f92591 ***

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

Always organize test artifacts in a directory hierarchy

When running tests in parallel, each test puts its generated files in a
different directory, under "outputs".  I think it would be nice if it
was always the case, as it would isolate the test cases a bit more.  An
artifact created by a test wouldn't get overwritten by another test.

Also, it makes it easier to clean up.  A lot of executables are left all
over the place because their names do not appear in gdb.*/Makefile.  If
everything is in "outputs", then we just have to delete that directory
(which we already do).

At the same time it makes the gdb.foo directories and their Makefiles
useless in the build directory, since they are pretty much only used for
cleaning.

What do you think?

gdb/testsuite/ChangeLog:

	* Makefile.in (ALL_SUBDIRS): Remove.
	(clean mostlyclean): Do not recurse in ALL_SUBDIRS.
	(distclean maintainer-clean realclean): Likewise.
	* configure.ac (AC_OUTPUT): Remove gdb.*/Makefile.
	* configure: Regenerate.
	* gdb.ada/Makefile.in: Delete.
	* gdb.arch/Makefile.in: Likewise.
	* gdb.asm/Makefile.in: Likewise.
	* gdb.base/Makefile.in: Likewise.
	* gdb.btrace/Makefile.in: Likewise.
	* gdb.cell/Makefile.in: Likewise.
	* gdb.compile/Makefile.in: Likewise.
	* gdb.cp/Makefile.in: Likewise.
	* gdb.disasm/Makefile.in: Likewise.
	* gdb.dlang/Makefile.in: Likewise.
	* gdb.dwarf2/Makefile.in: Likewise.
	* gdb.fortran/Makefile.in: Likewise.
	* gdb.gdb/Makefile.in: Likewise.
	* gdb.go/Makefile.in: Likewise.
	* gdb.guile/Makefile.in: Likewise.
	* gdb.java/Makefile.in: Likewise.
	* gdb.linespec/Makefile.in: Likewise.
	* gdb.mi/Makefile.in: Likewise.
	* gdb.modula2/Makefile.in: Likewise.
	* gdb.multi/Makefile.in: Likewise.
	* gdb.objc/Makefile.in: Likewise.
	* gdb.opencl/Makefile.in: Likewise.
	* gdb.opt/Makefile.in: Likewise.
	* gdb.pascal/Makefile.in: Likewise.
	* gdb.perf/Makefile.in: Likewise.
	* gdb.python/Makefile.in: Likewise.
	* gdb.reverse/Makefile.in: Likewise.
	* gdb.server/Makefile.in: Likewise.
	* gdb.stabs/Makefile.in: Likewise.
	* gdb.threads/Makefile.in: Likewise.
	* gdb.trace/Makefile.in: Likewise.
	* gdb.xml/Makefile.in: Likewise.
	* lib/gdb.exp (make_gdb_parallel_path): Add check for
	GDB_PARALLEL.
	(standard_output_file): Remove check for GDB_PARALLEL, always
	return path in outputs/$subdir/$testname.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow.
@ 2016-02-09 10:10 sergiodj+buildbot
  2016-02-09 11:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ea53e003163338a403d5afbb2046cafb8f3abe9 ***

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

Add a more helpful warning message to explain why some AArch64 relocations can overflow.

bfd	* elfnn-aarch64.c (elfNN_aarch64_relocate_section): Add a more
	helpful warning message to explain why certain AArch64 relocs
	might overflow.

ld	* testsuite/ld-aarch64/reloc-overflow-bad.d: New test.
	* testsuite/ld-aarch64/reloc-overflow-1.s: New source file.
	* testsuite/ld-aarch64/reloc-overflow-2.s: New source file.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix build breakage
@ 2016-02-09 10:38 sergiodj+buildbot
  2016-02-09 13:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 222cab58b7ed37df6e01dacb0932f400a2588137 ***

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

Fix build breakage

Add a cast to reinterpret a void* as a gdb_byte*.

2016-02-09  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/gdbserver/ChangeLog:

        * linux-x86-low.c (x86_siginfo_fixup): Add cast to gdb_byte*.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Revert "Add a more helpful warning message to explain why some AArch64 relocations can overflow."
@ 2016-02-09 10:48 sergiodj+buildbot
  2016-02-09 15:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0635c8759326e9431604b3359185cbf96740521d ***

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

Revert "Add a more helpful warning message to explain why some AArch64 relocations can overflow."

This reverts commit 2ea53e003163338a403d5afbb2046cafb8f3abe9.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Revert "Fix build breakage"
@ 2016-02-09 10:57 sergiodj+buildbot
  2016-02-09 16:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c23bbc1cdae6149de4175a75aa9bf9bcbc936fa4 ***

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

Revert "Fix build breakage"

This reverts commit 222cab58b7ed37df6e01dacb0932f400a2588137.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow.
@ 2016-02-09 11:06 sergiodj+buildbot
  2016-02-09 18:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 11:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 027e9c750c20fe8031a2b6d6272cd57bbf445df5 ***

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

Add a more helpful warning message to explain why some AArch64 relocations can overflow.

bfd	* elfnn-aarch64.c (elfNN_aarch64_relocate_section): Add a more
	helpful warning message to explain why certain AArch64 relocs
	might overflow.

ld	* testsuite/ld-aarch64/reloc-overflow-bad.d: New test.
	* testsuite/ld-aarch64/reloc-overflow-1.s: New source file.
	* testsuite/ld-aarch64/reloc-overflow-2.s: New source file.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't
@ 2016-02-09 12:41 sergiodj+buildbot
  2016-02-09 22:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 12:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a7f3dffced7a20c992e1488d9f05fed8b8001fd ***

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

Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't

PR19548 shows that we still have problems related to 13fd3ff34329:

 [PR17431: following execs with "breakpoint always-inserted on"]
 https://sourceware.org/ml/gdb-patches/2014-09/msg00733.html

The problem this time is that we currently update the global location
list and try to insert breakpoint locations after re-setting _each_
breakpoint in turn.

Say:

 - We have _more_ than one breakpoint set.  Let's assume 2.

 - There's a breakpoint with a pre-exec address that ends up being an
   unmapped address after the exec.

 - That breakpoint is NOT the first in the breakpoint list.

Then when handling an exec, and we re-set the first breakpoint in the
breakpoint list, we mistakently try to install the old pre-exec /
un-re-set locations of the other breakpoint, which fails:

 (gdb) continue
 Continuing.
 process 28295 is executing new program: (...)/execl-update-breakpoints2
 Error in re-setting breakpoint 1: Warning:
 Cannot insert breakpoint 2.
 Cannot access memory at address 0x1000764

 Breakpoint 1, main (argc=1, argv=0x7fffffffd368) at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.base/execl-update-breakpoints.c:34
 34        len = strlen (argv[0]);
 (gdb)

Fix this by deferring the global location list update till after all
breakpoints are re-set.

Tested on x86_64 Fedora 20, native and gdbserver.

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

	PR breakpoints/19548
	* breakpoint.c (create_overlay_event_breakpoint): Don't update
	global location list here.
	(create_longjmp_master_breakpoint)
	(create_std_terminate_master_breakpoint)
	(create_exception_master_breakpoint, create_jit_event_breakpoint)
	(update_breakpoint_locations):
	(breakpoint_re_set): Update global location list after all
	breakpoints are re-set.

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

	PR breakpoints/19548
	* gdb.base/execl-update-breakpoints.c (some_function): New
	function.
	(main): Call it.
	* gdb.base/execl-update-breakpoints.exp: Add a second breakpoint.
	Tighten expected GDB output.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Modernize configure.ac's
@ 2016-02-09 14:16 sergiodj+buildbot
  2016-02-10  0:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 14:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e94266c4db633f7defaf4bb68c74fd09a9cf9e2 ***

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

Modernize configure.ac's

Using AC_OUTPUT with arguments has been deprecated for some time in
autoconf, even in version 2.64, which we are using.  This change should
not affect functionality.

I also removed the "exit 0"'s, they shouldn't be necessary.

gdb/ChangeLog:

	* configure.ac: Use AC_CONFIG_FILES instead of passing arguments
	to AC_OUTPUT.  Remove "exit 0" at the end.
	* configure: Regenerate.

gdb/testsuite/ChangeLog:

	* configure.ac: Use AC_CONFIG_FILES instead of passing arguments
	to AC_OUTPUT.
	* configure: Regenerate.

gdb/gdbserver/ChangeLog:

	* configure.ac: Use AC_CONFIG_FILES instead of passing arguments
	to AC_OUTPUT.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix compile time warnings building the binutils with a gcc6 compiler.
@ 2016-02-09 16:46 sergiodj+buildbot
  2016-02-10  2:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 609332f15cc2ad651d0ebd573010595a4593e89a ***

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

Fix compile time warnings building the binutils with a gcc6 compiler.

include	* opcode/metag.h (metag_scondtab): Mark as possibly unused.
	* opcode/nds32.h (nds32_r45map): Likewise.
	(nds32_r54map): Likewise.
	* opcode/visium.h (gen_reg_table): Likewise.
	(fp_reg_table, cc_table, opcode_table): Likewise.

bfd	* oasys.c (oasys_archive_p): Fix indentation.
	* elf32-nds32.c (nds32_elf_relax_section): Use an unsigned
	constant for left shifting.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <8adce0342f5f50aba0154fc56ca59df45b219738@gdb-build>]
* [binutils-gdb] Refactor string_to_event_location for legacy linespec support.
@ 2016-02-09 22:48 sergiodj+buildbot
  2016-02-10  4:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 22:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eeb1af437c6f1ca111bc31b63eefc5344b553681 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: eeb1af437c6f1ca111bc31b63eefc5344b553681

Refactor string_to_event_location for legacy linespec support.

This patch refactors string_to_event_location, breaking it into two
separate functions:

1) string_to_event_location_basic
A "basic" string parser that implements support for "legacy" linespecs
(linespec, address, and probe locations).  This function is intended to
be used by any UI wishing/needing to support this legacy behavior.

2) string_to_event_location
This is now intended as a CLI-only function which adds explicit location
parsing in a CLI-appropriate manner (in the form of traditional option/value
pairs).

Together these patches serve to simplify string-to-event location parsing
for all existing non-CLI interfaces (MI, guile, and python).

gdb/ChangeLog

	* location.c (string_to_explicit_location): Note that "-p" is
	reserved for probe locations and return NULL for any input
	that starts with that.
	(string_to_event_location): Move "legacy" linespec code to ...
	(string_to_event_location_basic): ... here.
	* location.h (string_to_event_location): Update comment.
	(string_to_event_location_basic): New function.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use string_to_event_location_basic in guile.
@ 2016-02-09 23:05 sergiodj+buildbot
  2016-02-10  8:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 23:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a96e36da2f5278949099b0b985b2fa6ce474b135 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: a96e36da2f5278949099b0b985b2fa6ce474b135

Use string_to_event_location_basic in guile.

This patch, analogous to the previous python patch, implements proper
legacy linespec support in guile code using the newly introduced
string_to_event_location_basic.

gdb/ChangeLog

	* guile/scm-breakpoint.c (gdbscm_register_breakpoint_x): Skip
	leading whitespace and use string_to_event_location_basic instead
	of new_linespec_location.

gdb/testsuite/ChangeLog

	* gdb.guile/scm-breakpoint.exp (test_bkpt_address): New procedure.
	(toplevel): Call test_bkpt_address.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Enable/update legacy linespecs in MI.
@ 2016-02-09 23:32 sergiodj+buildbot
  2016-02-10  9:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 23:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39a67dc4f7d032c78f031e2d101b9552f1a6b57f ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 39a67dc4f7d032c78f031e2d101b9552f1a6b57f

Enable/update legacy linespecs in MI.

MI is currently using string_to_event_location to enable the use of legacy
linespecs, but using this function (until this patchset) had the (as yet
unnoticed) side effect of allowing both MI and CLI representation for
explicit locations.

This patch simply changes MI to use the same legacy linespec functions
that the python and guile interpreters use.  This eliminates the CLI syntax
for explicit locations (in MI).

gdb/ChangeLog

	* mi/mi-cmd-break.c (mi_cmd_break_insert_1): Use
	string_to_event_location_basic instead of string_to_event_location.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Update NEWS post GDB 7.11 branch creation.
@ 2016-02-10  4:06 sergiodj+buildbot
  2016-02-10 18:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  4:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1233c0bae644451922bda07d03f1a66f3439dd20 ***

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

Update NEWS post GDB 7.11 branch creation.

gdb/ChangeLog:

	* NEWS: Create a new section for the next release branch.
	Rename the section of the current branch, now that it has
	been cut.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Clear *VAL in regcache_raw_read_unsigned
@ 2016-02-10 17:06 sergiodj+buildbot
  2016-02-11 19:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f6a71b4bfdad8fa2fe33e86f799fa0d362973dc ***

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

Clear *VAL in regcache_raw_read_unsigned

We have function regcache_raw_read_unsigned defined in both GDB and
GDBserver, so that it is used in common like this,

  ULONGEST value;
  status = regcache_raw_read_unsigned (regcache, regnum, &value);

'value' is correctly set in GDB side, but may not be correctly set
in GDBserver, because &value is passed in regcache_raw_read_unsigned
but collect_register may only set part of the whole variable.  In my
test, I see the top half of 'value' is garbage.  This patch fixes this
problem by clearing *VAL before calling collect_register.

gdb/gdbserver:

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

	* regcache.c (regcache_raw_read_unsigned): Clear *VAL.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <473b99e5721ad623cc5826e03a73e2cf6cef4eb5@gdb-build>]
[parent not found: <62e5fd57bcdfb58eadd08ec430c4dfd742027d8e@gdb-build>]
* [binutils-gdb] Add missing quotes to gdb/testsuite/README
@ 2016-02-11 20:15 sergiodj+buildbot
  2016-02-12 15:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT acc23c113ab9602707574e7df120f96170a9731c ***

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

Add missing quotes to gdb/testsuite/README

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

	* README (Parallel testing): Add missing double quotes.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <9f5fed7852cae412443957862d759660cfcb3fd5@gdb-build>]
[parent not found: <7cae9051edc2e3b11b5c79c08edfb91ee7f4e2e4@gdb-build>]
[parent not found: <d21b5f15d92bc1902b9e57198f67550326c887d7@gdb-build>]
[parent not found: <020ecd38e74681cb14987baf1a4d3c3ee3be0006@gdb-build>]
* [binutils-gdb] testsuite: Fix false Fortran regressions with recent gcc
@ 2016-02-14  8:44 sergiodj+buildbot
  2016-02-14 13:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-14  8:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba881f505ba211ffee59e68617cd1a02a7b4737b ***

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

testsuite: Fix false Fortran regressions with recent gcc

gcc-4.9.2-6.fc21.x86_64 -> gcc-5.3.1-2.fc23.x86_64

-PASS: gdb.fortran/vla-ptype.exp: ptype pvla not initialized
+FAIL: gdb.fortran/vla-ptype.exp: ptype pvla not initialized
-PASS: gdb.fortran/vla-history.exp: print vla1 allocated
+FAIL: gdb.fortran/vla-history.exp: print vla1 allocated
-PASS: gdb.fortran/vla-history.exp: print $2
+FAIL: gdb.fortran/vla-history.exp: print $2
-PASS: gdb.fortran/vla-value.exp: print undefined pvla
+FAIL: gdb.fortran/vla-value.exp: print undefined pvla
-PASS: gdb.fortran/vla-value.exp: print non-associated &pvla
+FAIL: gdb.fortran/vla-value.exp: print non-associated &pvla
-PASS: gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)
+FAIL: gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)

These issues get fixed (or removed if no longer applicable) by attached patch.

It is based on Googled:
	http://www.cs.rpi.edu/~szymansk/OOF90/bugs.html#5
	When a pointer is declared its status is undefined, and cannot be
	safely queried with the associated intrinsic.
	-> nullify(VARNAME)
+
	https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/268786
	ALLOCATE is not supposed to initialize the array.
	-> Remove checks like an initial print is: \\( *0, *0, *0...\\)

These regressions remain:
	-PASS: gdb.fortran/library-module.exp: print var_i in lib
	+FAIL: gdb.fortran/library-module.exp: print var_i in lib
	-PASS: gdb.fortran/library-module.exp: print var_i in main
	+FAIL: gdb.fortran/library-module.exp: print var_i in main
I believe it is more a GDB bug (in a code contributed by me), filed:
	gdb.fortran/library-module.exp false regression on GCC upgrade
	https://sourceware.org/bugzilla/show_bug.cgi?id=19635

gdb/testsuite/ChangeLog
2016-02-14  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Fix compatibility with recent gfortran-5.3.1.
	* gdb.fortran/vla-history.exp (print vla1 allocated)
	(print vla2 allocated, print $2, print $3): Remove
	(print $4): Rename to ...
	(print $2): ... here.
	(print $9): Rename to ...
	(print $5): ... here.
	(print $10): Rename to ...
	(print $6): ... here.
	* gdb.fortran/vla.f90: Add pvla initialization.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Enhance GAS's .section directive so that it can take numeric values for the flags and type fields. (ELF only)
@ 2016-02-15 11:25 sergiodj+buildbot
  2016-02-15 14:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9fb71ee49fc37163697e4f34e16097928eb83d66 ***

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

Enhance GAS's .section directive so that it can take numeric values for the flags and type fields.  (ELF only)

gas	* doc/as.texinfo (.section): Document that numeric values can now
	be used for the flags and type fields of the ELF target's .section
	directive.  Add notes about the restrictions on setting flags and
	types.
	* config/obj-elf.c (obj_elf_change_section): Allow known sections
	to be given processor specific section types.  Allow processor and
	application specific flags of a section to be set after
	definition.
	(obj_elf_parse_section_letters): Handle parsing numeric values.
	(obj_elf_section_type): Handle parsing numeric values.
	(obj_elf_section): Allow numeric type values.
	* config/obj-elf.h (obj_elf_change_section): Update prototype.
	* testsuite/gas/elf/section10.d: New test.
	* testsuite/gas/elf/section10.s: Source file for new test.
	* testsuite/gas/elf/elf.exp: Run the new test.
	* testsuite/gas/i386/ilp32/x86-64-unwind.d: Remove dependency upon
	the description of the flags produced by readelf.
	* testsuite/gas/tic6x/scomm-directive-4.d: Likewise.
	* NEWS: Mention the new feature.

bfd	* elf-bfd.h (struct bfd_elf_special_section): Use unsigned values
	for length and type fields.  Use a signed value for the
	suffix_length field.

binutils* readelf.c (get_section_type_name): Add hex prefix to offsets
	printed for LOPROC and LOOS values.  Ensure that a result is
	always returned for the V850 target, even when an unrecognised
	processor specific value is encountered.
	(process_section_headers): Display key values in the order in
	which they appear to the user.  Add the "C (compressed)" value to
	the list.

ld	* testsuite/ld-i386/pr12718.d: Remove dependency upon the
	description of the flags produced by readelf.
	* testsuite/ld-i386/pr12921.d: Likewise.
	* testsuite/ld-i386/tlsbin-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsbin.rd: Likewise.
	* testsuite/ld-i386/tlsbindesc-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsbindesc.rd: Likewise.
	* testsuite/ld-i386/tlsdesc-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsdesc.rd: Likewise.
	* testsuite/ld-i386/tlsgdesc-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsgdesc.rd: Likewise.
	* testsuite/ld-i386/tlsnopic-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsnopic.rd: Likewise.
	* testsuite/ld-i386/tlspic-nacl.rd: Likewise.
	* testsuite/ld-i386/tlspic.rd: Likewise.
	* testsuite/ld-s390/tlsbin.rd: Likewise.
	* testsuite/ld-s390/tlsbin_64.rd: Likewise.
	* testsuite/ld-s390/tlspic.rd: Likewise.
	* testsuite/ld-s390/tlspic_64.rd: Likewise.
	* testsuite/ld-sh/tlsbin-2.d: Likewise.
	* testsuite/ld-sh/tlspic-2.d: Likewise.
	* testsuite/ld-tic6x/common.d: Likewise.
	* testsuite/ld-tic6x/shlib-1.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1b.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1r.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1rb.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1b.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1r.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1rb.rd: Likewise.
	* testsuite/ld-tic6x/shlib-noindex.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1b.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1r.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1rb.rd: Likewise.
	* testsuite/ld-x86-64/ilp32-4-nacl.d: Likewise.
	* testsuite/ld-x86-64/ilp32-4.d: Likewise.
	* testsuite/ld-x86-64/pr12718.d: Likewise.
	* testsuite/ld-x86-64/pr12921.d: Likewise.
	* testsuite/ld-x86-64/split-by-file-nacl.rd: Likewise.
	* testsuite/ld-x86-64/split-by-file.rd: Likewise.
	* testsuite/ld-x86-64/tlsbin-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsbin.rd: Likewise.
	* testsuite/ld-x86-64/tlsbindesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsbindesc.rd: Likewise.
	* testsuite/ld-x86-64/tlsdesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsdesc.rd: Likewise.
	* testsuite/ld-x86-64/tlsgdesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsgdesc.rd: Likewise.
	* testsuite/ld-x86-64/tlspic-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlspic.rd: Likewise.
	* testsuite/ld-xtensa/tlsbin.rd: Likewise.
	* testsuite/ld-xtensa/tlspic.rd: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Fix some tests that write outside of the standard output directory
@ 2016-02-15 17:01 sergiodj+buildbot
  2016-02-15 19:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa4803559b046ab4691965f8a4ceed1037b37629 ***

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

testsuite: Fix some tests that write outside of the standard output directory

gdb/testsuite/ChangeLog:

	* gdb.base/wrong_frame_bt_full.exp: Use standard_output_file to
	define object file path.
	* gdb.btrace/gcore.exp: Use standard_output_file to define core
	file path.
	* lib/opencl.exp (gdb_compile_opencl_hostapp): Use
	standard_output_file to define binfile.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add parentheses to prevent truncated addresses
@ 2016-02-16  0:16 sergiodj+buildbot
  2016-02-16  4:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-16  0:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fd7268abff6f99dbbb78505f095bf1f54064db7 ***

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

Add parentheses to prevent truncated addresses

	* i386-dis.c (print_insn): Parenthesize expression to prevent
	truncated addresses.
	(OP_J): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix BFD format matching for x86_64-w64-mingw32 -m32 LTO.
@ 2016-02-16  0:37 sergiodj+buildbot
  2016-02-16  5:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-16  0:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64bfc2584c013e7c60caceeffbad8250558e3cd2 ***

Author: Joseph Myers <joseph@codesourcery.com>
Branch: master
Commit: 64bfc2584c013e7c60caceeffbad8250558e3cd2

Fix BFD format matching for x86_64-w64-mingw32 -m32 LTO.

In <https://sourceware.org/ml/binutils/2015-12/msg00190.html> (commit
4a07dc81356ed8728e204e9aabeb256703c59aef), Kwok fixed a problem with
the template used for a dummy BFD for an IR file for LTO on MinGW,
where the input and output formats are not the same.

A problem, however, remains in the case of linking for
x86_64-w64-mingw32 -m32, where LTO linking reports an ambiguity
between the pe-i386 and pei-i386 formats.  An object (pe-i386) with
plugin data is being tested by the linker to see what formats match.
The default format initially set by the linker when
bfd_check_format_matches is called is pei-i386 (as that's the output
format from the linker script), which does not match, so the function
goes on to the loop over possible BFD vectors.  The pe-i386 vector
matches, as it should.  One other vector matches: the plugin vector.

bfd_check_format_matches tests a vector for matching by temporarily
modifying the BFD object to use that vector then using
_bfd_check_format on it.  So the BFD object is temporarily using
plugin_vec.  _bfd_check_format ends up using bfd_plugin_object_p which
uses plugin_object_p from ld which uses plugin_get_ir_dummy_bfd which
succeeds, having created a BFD based on link_info.output_bfd (because
srctemplate is the BFD temporarily using plugin_vec, even after Kwok's
patch link_info.output_bfd is all that's available to base the dummy
BFD on).  So we end up with a match from the plugin vector which uses
the pei-i386 vector even though the pei-i386 vector itself does not
match the input object.  (In the i686-mingw32 case, as opposed to this
multilib case, pe-i386 is the default BFD target, which would
short-circuit that logic.)

There are two cases of the linker handling inputs with a plugin: they
may be inputs that are also accepted by some non-plugin BFD format, as
here, or they may be a format that would not be recognized at all, as
with some tests in the ld testsuite.  In the former case, there is no
need for BFD to accept the objects using the plugin vector, as the
linker has its own logic to allow plugins to claim objects accepted by
some other BFD vector.  Thus, this patch arranges for the plugin
vector to have the lowest match priority, and for the priority from
that vector to be used in the relevant case (the attempted match to
the plugin vector results in TEMP pointing to the pei-i386 vector).

Tested for GCC and Binutils testsuites for x86_64-pc-linux-gnu, as
well as verifying that it fixes the observed LTO issue for
x86_64-w64-mingw32.

	* plugin.c (plugin_vec): Set match priority to 255.
	* format.c (bfd_check_format_matches) [BFD_SUPPORTS_PLUGINS]: When
	matching against the plugin vector, take priority from there not
	from TEMP.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Whitespace cleanup for skip testcase.
@ 2016-02-16 20:52 sergiodj+buildbot
  2016-02-17  3:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 20:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 21b1f8d2fc29b7e0585dbdca72c0b8a8bf070a2e ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 21b1f8d2fc29b7e0585dbdca72c0b8a8bf070a2e

Whitespace cleanup for skip testcase.

gdb/testsuite/ChangeLog:

	* gdb.base/skip.c: Add copyright.  Whitespace cleanup.
	* gdb.base/skip1.c: Ditto.
	* gdb.base/skip.exp: Whitespace cleanup.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add missing cleanup in exec_file_locate_attach
@ 2016-02-17 17:04 sergiodj+buildbot
  2016-02-17 18:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-17 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88178e828a0d1af133c19d6165e4d5ee59304adf ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 88178e828a0d1af133c19d6165e4d5ee59304adf

Add missing cleanup in exec_file_locate_attach

exec_file_locate_attach allocates memory for full_exec_path (using
either exec_file_find, source_full_path_of or xstrdup) but this
memory is never freed.  This commit adds the necessary cleanup.

gdb/ChangeLog:

	* exec.c (exec_file_locate_attach): Add missing cleanup.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Set breakpoint condition-evaluation in forking-threads-plus-breakpoint.exp
@ 2016-02-18 12:18 sergiodj+buildbot
  2016-02-18 14:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 12:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40fb20d037581bc9d4b17b6ab64ee98825cfacab ***

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

Set breakpoint condition-evaluation in forking-threads-plus-breakpoint.exp

Proc do_test in forking-threads-plus-breakpoint.exp has an argument
cond_bp_target, but the test doesn't use it to set
"breakpoint condition-evaluation", which is an oversight in the test.

This patch fixes it by setting "breakpoint condition-evaluation" per
$cond_bp_target.

gdb/testsuite:

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

	* gdb.threads/forking-threads-plus-breakpoint.exp (do_test):
	Set "set breakpoint condition-evaluation" per $cond_bp_target.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add D support to gdb_default_target_compile.
@ 2016-02-18 21:14 sergiodj+buildbot
  2016-02-19  0:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24f75eadabc519563ed119932c77874a016a799a ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 24f75eadabc519563ed119932c77874a016a799a

Add D support to gdb_default_target_compile.

gdb/testsuite/ChangeLog:

	* lib/future.exp: Add D support.
	(gdb_find_gdc): New proc.
	(gdb_default_target_compile): Add D support.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <f79a3bae8725dfe0e11b04ddfc6e6bc8f23e4e4e@gdb-build>]
* [binutils-gdb] Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary.
@ 2016-02-19 16:10 sergiodj+buildbot
  2016-02-19 19:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-19 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e517df3dbf7556ddb389228d713a804594ee3c1f ***

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

Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary.

	PR ld/19629
	* aoutx.h (aout_link_add_symbols): Check for out of range string
	table offsets.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove search_parents parameter from d_lookup_symbol_imports.
@ 2016-02-21 20:46 sergiodj+buildbot
  2016-02-21 21:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-21 20:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30a6a7f035026d05b52c92c26d4cb7ea3c6d6e5c ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 30a6a7f035026d05b52c92c26d4cb7ea3c6d6e5c

Remove search_parents parameter from d_lookup_symbol_imports.

gdb/ChangeLog:

	* d-namespace.c (d_lookup_symbol_imports): Remove argument
	'search_parents'.  All callers updated.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Also update recursive call to d_lookup_symbol_imports.
@ 2016-02-21 21:15 sergiodj+buildbot
  2016-02-21 22:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-21 21:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e08db6db1dd514f1c99f94bb6a9c1cfe02a1ab90 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: e08db6db1dd514f1c99f94bb6a9c1cfe02a1ab90

Also update recursive call to d_lookup_symbol_imports.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print'
@ 2016-02-22 16:37 sergiodj+buildbot
  2016-02-22 21:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac46107c5c781894e013b10cd9fb5c98a8393d26 ***

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

gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print'

After building GDB
	--with-python=/usr/bin/python3
and for example stripping ./gdb and running:
	./gdb -data-directory data-directory/ -iex "add-auto-load-safe-path $PWD/gdb-gdb.gdb" -iex "add-auto-load-safe-path $PWD/gdb-gdb.
py" ./gdb
I get:
	Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
	  File "/home/jkratoch/redhat/gdb-test-python3/gdb/gdb-gdb.py", line 91
	    print "Warning: Cannot find enum type_flag_value type."
								  ^
	SyntaxError: Missing parentheses in call to 'print'
	(top-gdb) q

gdb/ChangeLog
2016-02-22  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb-gdb.py (class TypeFlagsPrinter): Use parentheses for print.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Make linker assigned symbol dynamic only for shared object
@ 2016-02-23 13:32 sergiodj+buildbot
  2016-02-23 16:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b3b0ab89663306d17927d630304dbbd36e84570 ***

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

Make linker assigned symbol dynamic only for shared object

Linker assigned symbols should be made dynamic by default only when
creating shared object or relocatable executable.

bfd/

	* elflink.c (bfd_elf_record_link_assignment): Check for shared
	library, instead of PIC, and don't check PDE when making linker
	assigned symbol dynamic.

ld/

	* testsuite/ld-frv/fdpic-pie-6.d: Updated.
	* testsuite/ld-mips-elf/pie-n32.d: Likewise.
	* testsuite/ld-mips-elf/pie-n64.d: Likewise.
	* testsuite/ld-mips-elf/pie-o32.d: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arm-tdep.c: Remove unused "to" parameters
@ 2016-02-23 18:34 sergiodj+buildbot
  2016-02-23 20:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 18:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1254566561957d2202d61e12881b0eb40d33a64c ***

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

arm-tdep.c: Remove unused "to" parameters

gdb/ChangeLog:

	* arm-tdep.c (arm_decode_svc_copro): Remove "to" parameter.
	(thumb_process_displaced_insn): Likewise.
	(arm_process_displaced_insn): Adjust calls.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Extend "skip" command to support -file, -gfile, -function, -rfunction.
@ 2016-02-23 21:37 sergiodj+buildbot
  2016-02-23 23:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 21:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cce0e92333b872cfe036aae611b6b5d61cf58186 ***

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

Extend "skip" command to support -file, -gfile, -function, -rfunction.

gdb/ChangeLog:

	Extend "skip" command to support -file, -gfile, -function, -rfunction.
	* NEWS: Document new features.
	* skip.c: #include "fnmatch.h", "gdb_regex.h".
	(skiplist_entry) <file>: Renamed from filename.
	<function>: Renamed from function_name.
	<file_is_glob, function_is_regexp>: New members.
	<compiled_function_regexp, compiled_function_regexp_is_valid>:
	New members.
	(make_skip_entry): New function.
	(free_skiplist_entry, free_skiplist_entry_cleanup): New functions.
	(make_free_skiplist_entry_cleanup): New function.
	(skip_file_command): Update.
	(skip_function, skip_function_command): Update.
	(compile_skip_regexp): New functions.
	(skip_command): Add support for new options.
	(skip_info): Update.
	(skip_file_p, skip_gfile_p): New functions.
	(skip_function_p, skip_rfunction_p): New functions.
	(function_name_is_marked_for_skip): Update and simplify.
	(_initialize_step_skip): Update.
	* symtab.c: #include "fnmatch.h".
	(compare_glob_filenames_for_search): New function.
	* symtab.h (compare_glob_filenames_for_search): Declare.
	* utils.c (count_path_elements): New function.
	(strip_leading_path_elements): New function.
	* utils.h (count_path_elements): Declare.
	(strip_leading_path_elements): Declare.

gdb/doc/ChangeLog:

	* gdb.texinfo (Skipping Over Functions and Files): Document new
	options to "skip" command.  Update docs of output of "info skip".

gdb/testsuite/ChangeLog:

	* gdb.base/skip.c (test_skip): New function.
	(end_test_skip_file_and_function): New function.
	(test_skip_file_and_function): New function.
	* gdb.base/skip1.c (test_skip): New function.
	(skip1_test_skip_file_and_function): New function.
	* gdb.base/skip.exp: Add tests for new skip options.
	* gdb.base/skip-solib.exp: Update expected output.
	* gdb.perf/skip-command.cc: New file.
	* gdb.perf/skip-command.exp: New file.
	* gdb.perf/skip-command.py: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Build unavailable-stack frames for tracepoint.
@ 2016-02-24  3:22 sergiodj+buildbot
  2016-02-24  4:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-24  3:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50ae56ec464580492a5f987f658acc6ad82131b6 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: 50ae56ec464580492a5f987f658acc6ad82131b6

Build unavailable-stack frames for tracepoint.

gdb/ChangeLog:

2016-02-24  Wei-cheng Wang  <cole945@gmail.com>

	* rs6000-tdep.c (rs6000_frame_cache, rs6000_frame_this_id): Handle
	unavailable PC/SP to build unavailable frame.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2
@ 2016-02-24 14:09 sergiodj+buildbot
  2016-02-24 20:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8afc7bea4018bf535902503c9a25dd4a96dfa3ca ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 8afc7bea4018bf535902503c9a25dd4a96dfa3ca

[OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (print_insn_coprocessor): Check co-processor number for
	cpd/cpd2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2.

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/copro.s: Use coprocessor other than 10, 11.
	* testsuite/gas/arm/copro.d: Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support.
@ 2016-02-24 14:22 sergiodj+buildbot
  2016-02-24 23:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b0c11777665276f8e9b590bbe4832a7c66f5093d ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: b0c11777665276f8e9b590bbe4832a7c66f5093d

[OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support.

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (coprocessor_opcodes): Add fp16 instruction entries.
	(print_insn_coprocessor): Support fp16 instruction.

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/copro.d: Adjust output.
	* testsuite/gas/arm/copro.s: Adjust co-processor num.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] powerpc: Support z-point type in gdbserver.
@ 2016-02-24 17:45 sergiodj+buildbot
  2016-02-25  3:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 17:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 657f9cde9d531c9929bef9e02a8064101d568f50 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: 657f9cde9d531c9929bef9e02a8064101d568f50

powerpc: Support z-point type in gdbserver.

Support z-point, so tracepoints and breakpoints can be inserted at the same
location.

gdb/gdbserver/ChangeLog:

2016-02-24  Wei-cheng Wang  <cole945@gmail.com>

	* linux-ppc-low.c (ppc_supports_z_point_type): New function:
	(ppc_insert_point, ppc_remove_point): Insert/remove z-packet breakpoints.
	(ppc64_emit_ops_vector): Add target ops - ppc_supports_z_point_type,
	ppc_insert_point, ppc_remove_point.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Move new skip features to proper section (post 7.11).
@ 2016-02-24 18:24 sergiodj+buildbot
  2016-02-25  5:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2dffb8d3be366d4d02de06e92c24c9abdb0adfc ***

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

Move new skip features to proper section (post 7.11).


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <338435ef105ff51e967571ad073830ec1eb5a4ab@gdb-build>]
* [binutils-gdb] Add elf_x86_64_need_pic
@ 2016-02-25 12:24 sergiodj+buildbot
  2016-02-25 14:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 12:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef77d6af7cade17c566e4d1ecff098b841972f17 ***

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

Add elf_x86_64_need_pic

Add elf_x86_64_need_pic and replace x86_64_elf_howto_table[r_type].name
with howto->name.

	* elf64-x86-64.c (elf_x86_64_need_pic): New function.
	(elf_x86_64_relocate_section): Use it.  Replace
	x86_64_elf_howto_table[r_type] with howto.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] avoid compiler warnings in remote-m32r-sdi.c
@ 2016-02-25 17:42 sergiodj+buildbot
  2016-02-26  3:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1547ef64562ebbfcdc768ce93979f09bdd119b11 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 1547ef64562ebbfcdc768ce93979f09bdd119b11

avoid compiler warnings in remote-m32r-sdi.c

gdb/ChangeLog:

	* remote-m32r-sdi.c (recv_char_data): Initialize val to avoid
	compiler warning.
	(recv_long_data): Ditto.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <7337a6f2297cdd91bb852b479b284e5796d62cc9@gdb-build>]
* [binutils-gdb] Properly implement STT_COMMON
@ 2016-02-26 14:51 sergiodj+buildbot
  2016-02-26 18:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 14:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8871f357fdfa9c0c06d2d3e5600391d8c994f37 ***

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

Properly implement STT_COMMON

The BFD configure option, --enable-elf-stt-common, can't be to used to
verify STT_COMMON implementation with the normal binutils build.  Instead,
this patch removes it from BFD.  It adds --elf-stt-common=[no|yes] to ELF
assembler/objcopy and adds -z common/-z nocommon to ld.

A configure option, --enable-elf-stt-common, is added to gas to specify
whether ELF assembler should generate common symbols with the STT_COMMON
type by default.

Since BSF_KEEP_G is never used, it is renamed to BSF_ELF_COMMON for ELF
common symbols.

bfd/

	PR ld/19645
	* bfd.c (bfd): Change flags to 20 bits.
	(BFD_CONVERT_ELF_COMMON): New.
	(BFD_USE_ELF_STT_COMMON): Likewise.
	(BFD_FLAGS_SAVED): Add BFD_CONVERT_ELF_COMMON and
	BFD_USE_ELF_STT_COMMON.
	(BFD_FLAGS_FOR_BFD_USE_MASK): Likewise.
	* configure.ac: Remove --enable-elf-stt-common.
	* elf.c (swap_out_syms): Choose STT_COMMON or STT_OBJECT for
	common symbol depending on BFD_CONVERT_ELF_COMMON and
	BFD_USE_ELF_STT_COMMON.
	* elfcode.h (elf_slurp_symbol_table): Set BSF_ELF_COMMON for
	STT_COMMON.
	* elflink.c (bfd_elf_link_mark_dynamic_symbol): Also check
	STT_COMMON.
	(elf_link_convert_common_type): New function.
	(elf_link_output_extsym): Choose STT_COMMON or STT_OBJECT for
	common symbol depending on BFD_CONVERT_ELF_COMMON and
	BFD_USE_ELF_STT_COMMON.  Set sym.st_info after sym.st_shndx.
	* elfxx-target.h (TARGET_BIG_SYM): Add BFD_CONVERT_ELF_COMMON
	and BFD_USE_ELF_STT_COMMON to object_flags.
	(TARGET_LITTLE_SYM): Likewise.
	* syms.c (BSF_KEEP_G): Renamed to ...
	(BSF_ELF_COMMON): This.
	* bfd-in2.h: Regenerated.
	* config.in: Likewise.
	* configure: Likewise.

binutils/

	PR ld/19645
	* NEWS: Mention --elf-stt-common= for objcopy.
	* doc/binutils.texi: Document --elf-stt-common= for objcopy.
	* objcopy.c (do_elf_stt_common): New.
	(command_line_switch): Add OPTION_ELF_STT_COMMON.
	(copy_options): Add --elf-stt-common=.
	(copy_usage): Add --elf-stt-common=.
	(copy_object): Also check do_elf_stt_common for ELF targets.
	(copy_file): Handle do_elf_stt_common.
	(copy_main): Handle OPTION_ELF_STT_COMMON.
	* readelf.c (apply_relocations): Support STT_COMMON.
	* testsuite/binutils-all/common-1.s: New file.
	* testsuite/binutils-all/common-1a.d: Likewise.
	* testsuite/binutils-all/common-1b.d: Likewise.
	* testsuite/binutils-all/common-1c.d: Likewise.
	* testsuite/binutils-all/common-1d.d: Likewise.
	* testsuite/binutils-all/common-1e.d: Likewise.
	* testsuite/binutils-all/common-1f.d: Likewise.
	* testsuite/binutils-all/common-2.s: Likewise.
	* testsuite/binutils-all/common-2a.d: Likewise.
	* testsuite/binutils-all/common-2b.d: Likewise.
	* testsuite/binutils-all/common-2c.d: Likewise.
	* testsuite/binutils-all/common-2d.d: Likewise.
	* testsuite/binutils-all/common-2e.d: Likewise.
	* testsuite/binutils-all/common-2f.d: Likewise.
	* testsuite/binutils-all/objcopy.exp
	(objcopy_test_elf_common_symbols): New proc.
	Run objcopy_test_elf_common_symbols for ELF targets

gas/

	PR ld/19645
	* NEWS: Mention --enable-elf-stt-common and --elf-stt-common=
	for ELF assemblers.
	* as.c (flag_use_elf_stt_common): New.
	(show_usage): Add --elf-stt-common=.
	(option_values): Add OPTION_ELF_STT_COMMON.
	(std_longopts): Add --elf-stt-common=.
	(parse_args): Handle --elf-stt-common=.
	* as.h (flag_use_elf_stt_common): New.
	* config.in: Regenerated.
	* configure: Likewise.
	* configure.ac: Add --enable-elf-stt-common and define
	DEFAULT_GENERATE_ELF_STT_COMMON.
	* gas/write.c (write_object_file): Set BFD_CONVERT_ELF_COMMON
	and BFD_USE_ELF_STT_COMMON if flag_use_elf_stt_common is set.
	* doc/as.texinfo: Document --elf-stt-common=.
	* testsuite/gas/elf/common3.s: New file.
	* testsuite/gas/elf/common3a.d: Likewise.
	* testsuite/gas/elf/common3b.d: Likewise.
	* testsuite/gas/elf/common4.s: Likewise.
	* testsuite/gas/elf/common4a.d: Likewise.
	* testsuite/gas/elf/common4b.d: Likewise.
	* testsuite/gas/i386/dw2-compress-3b.d: Likewise.
	* testsuite/gas/i386/dw2-compressed-3b.d: Likewise.
	* testsuite/gas/elf/elf.exp: Run common3a, common3b, common4a
	and common4b.
	* testsuite/gas/i386/dw2-compress-3.d: Renamed to ...
	* testsuite/gas/i386/dw2-compress-3a.d: This.  Pass
	--elf-stt-common=no to as.
	* testsuite/gas/i386/dw2-compressed-3.d: Renamed to ...
	* testsuite/gas/i386/dw2-compressed-3a.d: This.  Pass
	--elf-stt-common=no to as.
	* testsuite/gas/i386/i386.exp: Run dw2-compress-3a,
	dw2-compress-3b, dw2-compressed-3a and dw2-compressed-3b instead
	of dw2-compress-3 and dw2-compressed-3.

include/

	PR ld/19645
	* bfdlink.h (bfd_link_elf_stt_common): New enum.
	(bfd_link_info): Add elf_stt_common.

ld/

	PR ld/19645
	* NEWS: Mention -z common/-z nocommon for ELF targets.
	* emultempl/elf32.em (gld${EMULATION_NAME}_handle_option): Handle
	-z common and -z nocommon.
	* ld.texinfo: Document -z common/-z nocommon.
	* lexsup.c (elf_shlib_list_options): Add -z common/-z nocommon.
	* testsuite/ld-elf/tls_common.exp: Test --elf-stt-common=no and
	--elf-stt-common=yes with assembler.
	* testsuite/ld-elfcomm/common-1.s: New file.
	* testsuite/ld-elfcomm/common-1a.d: Likewise.
	* testsuite/ld-elfcomm/common-1b.d: Likewise.
	* testsuite/ld-elfcomm/common-1c.d: Likewise.
	* testsuite/ld-elfcomm/common-1d.d: Likewise.
	* testsuite/ld-elfcomm/common-1e.d: Likewise.
	* testsuite/ld-elfcomm/common-1f.d: Likewise.
	* testsuite/ld-elfcomm/common-2.s: Likewise.
	* testsuite/ld-elfcomm/common-2a.d: Likewise.
	* testsuite/ld-elfcomm/common-2b.d: Likewise.
	* testsuite/ld-elfcomm/common-2c.d: Likewise.
	* testsuite/ld-elfcomm/common-2d.d: Likewise.
	* testsuite/ld-elfcomm/common-2e.d: Likewise.
	* testsuite/ld-elfcomm/common-2f.d: Likewise.
	* testsuite/ld-elfcomm/common-3a.rd: Likewise.
	* testsuite/ld-elfcomm/common-3b.rd: Likewise.
	* testsuite/ld-i386/pr19645.d: Likewise.
	* testsuite/ld-i386/pr19645.s: Likewise.
	* testsuite/ld-x86-64/largecomm-1.s: Likewise.
	* testsuite/ld-x86-64/largecomm-1a.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1b.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1c.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1d.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1e.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1f.d: Likewise.
	* testsuite/ld-x86-64/pr19645.d: Likewise.
	* testsuite/ld-x86-64/pr19645.s: Likewise.
	* testsuite/ld-elfcomm/elfcomm.exp: Test --elf-stt-common=yes
	with assembler.
	(assembler_generates_commons): Removed.
	Run -z common/-z nocommon tests.  Run *.d tests.
	* testsuite/ld-i386/i386.exp: Run pr19645.
	* testsuite/ld-x86-64/x86-64.exp: Likewise.
	* testsuite/ld-x86-64/dwarfreloc.exp: Test --elf-stt-common with
	assembler.  Test STT_COMMON with readelf.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add x86_64-*-rtems* target
@ 2016-02-26 20:20 sergiodj+buildbot
  2016-02-27  6:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 20:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f73dbb0e48ef50d2743fed89b68530b731329f05 ***

Author: Joel Sherrill <joel.sherrill@oarcorp.com>
Branch: master
Commit: f73dbb0e48ef50d2743fed89b68530b731329f05

Add x86_64-*-rtems* target

	ld/configure.tgt: Also add stanza for x86_64-*-elf.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't recursively look for a symbol in all imports of imported modules.
@ 2016-02-28 15:25 sergiodj+buildbot
  2016-02-28 16:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-28 15:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 38899f16e1560ce3020bab8a6a0b3a0c017d7925 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 38899f16e1560ce3020bab8a6a0b3a0c017d7925

Don't recursively look for a symbol in all imports of imported modules.

Given two or more modules that import each other's scope, the current symbol
lookup routines would go round in circles looking through each import from
each module, possibly checking the same module twice or more until all possible
paths are marked as "searched".

Given enough modules, this causes an exponential slowdown in time taken to find
symbols that do exist, and infinite recursion when they don't.

gdb/ChangeLog:
	* d-namespace.c (d_lookup_symbol_imports): Avoid recursive lookups from
	cyclic imports.

gdb/testsuite/ChangeLog:
	* gdb.dlang/circular.c: New file.
	* gdb.dlang/circular.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Support more syscalls in linux-record: pipe2 epoll_create1 eventfd2 fallocate dup3 and inotify_init1
@ 2016-02-29 16:58 sergiodj+buildbot
  2016-02-29 20:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 16:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 253b4d3a09e9edbb72d21127fbc85934ab1b7c07 ***

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

Support more syscalls in linux-record: pipe2 epoll_create1 eventfd2 fallocate dup3 and inotify_init1

This patch adds more syscalls in linux-record.

gdb:

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

	* linux-record.h (enum gdb_syscall) <gdb_sys_fallocate>: New.
	<gdb_sys_eventfd2, gdb_sys_epoll_create1, gdb_sys_dup3>: New.
	<gdb_sys_pipe2, gdb_sys_inotify_init1>: New.
	* linux-record.c (record_linux_system_call): Handle them.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] aarch64-linux process record: more syscalls
@ 2016-02-29 17:29 sergiodj+buildbot
  2016-03-01 10:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d521906965b3e94648a723a13576236aaba301d0 ***

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

aarch64-linux process record: more syscalls

The last patch supports several syscalls in linux-record.c, so now
GDB aarch64-linux backend can return these canonicalized syscall numbers
per aarch64 syscall number.

This patch fixes the following fails,

Process record and replay target doesn't support syscall number 59^M
Process record: failed to record execution log.^M
^M
Program stopped.^M
0x00000020000eab28 in pipe () from /lib/aarch64-linux-gnu/libc.so.6^M
(gdb) FAIL: gdb.reverse/pipe-reverse.exp: continue to breakpoint: marker2

Process record and replay target doesn't support syscall number 59^M
Process record: failed to record execution log.^M
^M
Program stopped.^M
0x00000020000eab28 in pipe () from /lib/aarch64-linux-gnu/libc.so.6^M
(gdb) FAIL: gdb.reverse/readv-reverse.exp: continue to breakpoint: marker2

gdb:

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

	* aarch64-linux-tdep.c (aarch64_canonicalize_syscall): Support
	eventfd2, eventfd2, dup3, inotify_init1, fallocate and pipe2.
	Return gdb_sys_epoll_create1 instead of gdb_sys_epoll_create
	for aarch64_sys_epoll_create1.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] S390: Fix internal error with stackless inferior
@ 2016-03-01 11:55 sergiodj+buildbot
  2016-03-01 14:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f24894771e384b1bc60dc0f2c104d7e7fad3c865 ***

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

S390: Fix internal error with stackless inferior

This fixes a GDB internal error that may occur when the inferior has no
valid stack pointer in r15.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-stackless.S: New.
	* gdb.arch/s390-stackless.exp: New.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_backchain_frame_unwind_cache): Avoid
	exception when attempting to access the inferior's backchain.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] S390: Fix output path for s390-tdbregs test case
@ 2016-03-01 12:05 sergiodj+buildbot
  2016-03-01 16:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a9321595003d86dd4794d0edab071f91989808e ***

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

S390: Fix output path for s390-tdbregs test case

Since test artifacts are always organized in a directory hierarchy, the
s390-tdbregs test case is not executed correctly any more.  This is
because it uses an obsolete way of constructing the executable's path.

This change invokes prepare_for_testing instead.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-tdbregs.exp: Use prepare_for_testing instead of
	manually constructing the output path.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix output path for arm-disp-step.exp
@ 2016-03-01 15:41 sergiodj+buildbot
  2016-03-01 19:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 15:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30ca9da1193ec4c82cc67a2ec2e6fb6adac7ab84 ***

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

Fix output path for arm-disp-step.exp

This patch fixes the following error,

ERROR: (/scratch/yao/gdb/build-git/arm-linux-gnueabihf/gdb/testsuite/outputs/gdb.arch/arm-disp-step/arm-disp-step) No such file or directory
FAIL: gdb.arch/arm-disp-step.exp: Can't run to main

gdb/testsuite:

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

	* gdb.arch/arm-disp-step.exp: Use standard_testfile and
	prepare_for_testing.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdb.threads/watchpoint-fork*.c compilation
@ 2016-03-01 17:53 sergiodj+buildbot
  2016-03-01 22:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 17:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e903e320352db86233e1dd2d10fd140f5d4a887 ***

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

Fix gdb.threads/watchpoint-fork*.c compilation

This testcase currently fails to compile on Fedora 23:

 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c: In function 'start':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:70:11: warning: implicit declaration of function 'pthread_yield' [-Wimplicit-function-declaration]
	i = pthread_yield ();
	    ^
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-child.c: In function 'forkoff':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-child.c:114:8: warning: implicit declaration of function 'pthread_yield' [-Wimplicit-function-declaratio
 n]
     i = pthread_yield ();
	 ^
 /tmp/ccUkNIsI.o: In function `start':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:70: undefined reference to `pthread_yield'
 (...)
 collect2: error: ld returned 1 exit status

 UNSUPPORTED: gdb.threads/watchpoint-fork.exp: child: multithreaded: Couldn't compile watchpoint-fork-child.c: unrecognized error
 UNTESTED: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint-fork.exp
 testcase .../src/gdb/testsuite/gdb.threads/watchpoint-fork.exp completed i

The glibc manual says, on _GNU_SOURCE:

 "You should define these macros by using #define preprocessor
 directives at the top of your source code files. These directives must
 come before any #include of a system header file."

I instead put it in the header all the .c files of the testcase must
include anyway.

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

	* gdb.threads/watchpoint-fork-child.c: Include "watchpoint-fork.h"
	before anything else.
	* gdb.threads/watchpoint-fork-mt.c: Likewise.  Don't define
	_GNU_SOURCE here.
	* gdb.threads/watchpoint-fork-st.c: Include "watchpoint-fork.h"
	before anything else.
	* gdb.threads/watchpoint-fork.h: Define _GNU_SOURCE.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdb.trace/ftrace-lock.c compilation
@ 2016-03-01 18:47 sergiodj+buildbot
  2016-03-02  3:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86e501afd46d7f0d31738bd62457593401d79bad ***

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

Fix gdb.trace/ftrace-lock.c compilation

Fixes, on F23:

 .../src/gdb/testsuite/gdb.trace/ftrace-lock.c: In function 'gdb_agent_gdb_collect':
 .../src/gdb/testsuite/gdb.trace/ftrace-lock.c:50:3: warning: implicit declaration of function 'sleep' [-Wimplicit-function-declaration]
    sleep (1);
    ^

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

	* gdb.trace/ftrace-lock.c: Include <unistd.h>.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Regenerate bfd files.
@ 2016-03-02  4:03 sergiodj+buildbot
  2016-03-02  6:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-02  4:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70a5df4fe30fd37166c3b62071fd816e49082d2e ***

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

Regenerate bfd files.

	* Makefile.in: Regenerate.
	* po/SRC-POTFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Remove unnecessary code in fortran vla-history test.
@ 2016-03-02 16:16 sergiodj+buildbot
  2016-03-03  1:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 16:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 065ab6dc804575bce7df58477b2cfcb2b2a6eafb ***

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

testsuite: Remove unnecessary code in fortran vla-history test.

testsuite: Remove unnecessary code in fortran vla-history test.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.fortran/vla-history.exp: Remove breakpoint.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded.
@ 2016-03-02 16:31 sergiodj+buildbot
  2016-03-03  3:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 16:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6896a8fa1e1d24a8fcc9b30efc0b195246b46029 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 6896a8fa1e1d24a8fcc9b30efc0b195246b46029

[OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded.

Fixes rather embarassing gdb.trace regressions.

gdb/gdbserver/ChangeLog:

	* tracepoint.c (cmd_qtstart): Only set ipa_tdesc_idx if agent
	is actually loaded.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Fix timeout issues during print of vla-arrays.
@ 2016-03-02 17:06 sergiodj+buildbot
  2016-03-03  0:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07e448ade17bc8fb52469a5b2184017f94669bd6 ***

Author: bernhard.heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 07e448ade17bc8fb52469a5b2184017f94669bd6

testsuite: Fix timeout issues during print of vla-arrays.

Printing and resolving of dynamic array's causes sporadic timeout issues on loaded systems.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.fortran/vla-history.exp: Lookup array elements and printing exceeds timeout.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Refactor gdb.base/disp-step-syscall.exp for general step over test
@ 2016-03-03  9:42 sergiodj+buildbot
  2016-03-03 12:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-03  9:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b47da9f176aa73854f1ff8ae00afda11a4f338a ***

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

Refactor gdb.base/disp-step-syscall.exp for general step over test

This patch moves some code out of disp_step_cross_syscall to a new proc
check_pc_after_cross_syscall and setup.  Procedure setup is to start a
fresh GDB and compute the syscall instruction address.

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp (check_pc_after_cross_syscall): New
	proc.
	(setup): New proc.
	(disp_step_cross_syscall): Move code to check_pc_after_cross_syscall
	and setup.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Step over syscalll insn with disp-step on and off
@ 2016-03-03  9:51 sergiodj+buildbot
  2016-03-03 14:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-03  9:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e197ad3c87723a2bdf383d38fcfa3eaa4fa1ba12 ***

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

Step over syscalll insn with disp-step on and off

disp-step-syscall.exp was added to test displaced stepping over syscall
instructions, in which we set breakpoint on syscall instruction, and
step over it.  In fact, we can extend the test to non-displaced-stepping
case.  This patch wraps the test with displaced stepping on and off.
Note that the indentation and format isn't adjusted here to make this
patch easy to read.  The following patch will fix the format separately.

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp: Don't invoke
	support_displaced_stepping.
	(disp_step_cross_syscall): Test with displaced stepping off and
	on if supported.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Step over fork/vfork syscall insn in gdbserver
@ 2016-03-03 10:00 sergiodj+buildbot
  2016-03-03 16:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92fa70b0bd8690d979357ebcdb501a9e4aa42ea6 ***

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

Step over fork/vfork syscall insn in gdbserver

We can also extend disp-step-syscall.exp to test GDBserver step over
breakpoint on syscall instruction.  That is, we set a breakpoint
with a false condition on syscall instruction, so that GDBserver will
step over it.

This test triggers a GDBserver internal error, which can be fixed by
this series.

(gdb) PASS: gdb.base/disp-step-syscall.exp: fork: break cond on target: break on syscall insns
continue^M
Continuing.^M
Remote connection closed^M
(gdb) FAIL: gdb.base/disp-step-syscall.exp: fork: break cond on target: continue to fork again

In GDBserver, there is an internal error,

/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:1922: A problem internal to GDBserver has been detected.
unsuspend LWP 25554, suspended=-1

the simplified reproducer is like,

$ ./gdb ./testsuite/outputs/gdb.base/disp-step-syscall/disp-step-fork
(gdb) b main
(gdb) c
(gdb) disassemble fork // in order to find the address of insn 'syscall'
....
   0x00007ffff7ad6023 <+179>:	syscall
(gdb) b *0x00007ffff7ad6023 if main == 0
(gdb) c

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp (break_cond_on_syscall): New.
	If target supports condition evaluation on target, invoke
	break_cond_on_syscall for fork and vfork.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Rename disp-step-syscall.exp to step-over-syscall.exp
@ 2016-03-03 10:09 sergiodj+buildbot
  2016-03-03 17:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8fc8cbdaf698ed042d859d5749cff66937bbb57c ***

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

Rename disp-step-syscall.exp to step-over-syscall.exp

disp-step-syscall.exp is extended for stepping over syscall instruction
in different cases, with or without displaced stepping, and stepping
over by GDBserver.

This patch rename disp-step-syscall.exp to step-over-syscall.exp to
reflect this.

gdb/testsuite:

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

	* gdb.base/disp-step-fork.c: Rename to ...
	* gdb.base/step-over-fork.c: ... it.  New file.
	* gdb.base/disp-step-vfork.c: Rename to ...
	* gdb.base/step-over-vfork.c: ... it.  New file.
	* gdb.base/disp-step-syscall.exp: Rename to ...
	* gdb.base/step-over-syscall.exp: ... it.  New file.
	(disp_step_cross_syscall): Rename to ...
	(step_over_syscall): ... it.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Reformat gdb.base/step-over-syscall.exp
@ 2016-03-03 10:20 sergiodj+buildbot
  2016-03-03 19:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea50786226737509a8f4c2734699a5fc15cc63c4 ***

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

Reformat gdb.base/step-over-syscall.exp

gdb/testsuite:

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

	* gdb.base/step-over-syscall.exp (disp_step_cross_syscall): Fix
	code format.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions.
@ 2016-03-03 15:34 sergiodj+buildbot
  2016-03-04  1:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57aa17424380be1c3e362a5601071f1f3a6f74f6 ***

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

Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions.

	* simulator.c (set_flags_for_sub32): Correct type of signbit.
	(CondCompare): Swap interpretation of bit 30.
	(DO_ADDP): Delete macro.
	(do_vec_ADDP): Copy source registers before starting to update
	destination register.
	(do_vec_FADDP): Likewise.
	(do_vec_load_store): Fix computation of sizeof_operation.
	(rbit64): Fix type of constant.
	(aarch64_step): When displaying insn value, display all 32 bits.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb.base/skip.exp: Use with_test_prefix.
@ 2016-03-03 19:03 sergiodj+buildbot
  2016-03-04  2:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 19:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdf7e23048b68171c01f2498cc46670a76e68c4d ***

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

gdb.base/skip.exp: Use with_test_prefix.

gdb/testsuite/ChangeLog:

	* gdb.base/skip.exp: Use with_test_prefix.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] get_symbols() plugin API tweak to support --start-lib/--end-lib.
@ 2016-03-03 21:03 sergiodj+buildbot
  2016-03-04  4:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 21:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95ecdfbfcbf508919652a0254ee2b8c6572a949e ***

Author: Evgenii Stepanov <eugenis@google.com>
Branch: master
Commit: 95ecdfbfcbf508919652a0254ee2b8c6572a949e

get_symbols() plugin API tweak to support --start-lib/--end-lib.

Let the plugin know that a file is not being included in the link by
returning LDPS_NO_SYMS from get_symbols().

include/
	* plugin-api.h (enum ld_plugin_tag): Add LDPT_GET_SYMBOLS_V3.

gold/
	* plugin.h (Pluginobj::get_symbol_resolution_info): Add version
	parameter.
	* plugin.cc (get_symbols_v3): New function.
	(Plugin::load): Add LDPT_GET_SYMBOLS_V3.
	(Pluginobj::get_symbol_resolution_info): Return LDPS_NO_SYMS when using
	new version.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add new plugin hooks to support querying section alignment and size.
@ 2016-03-03 21:12 sergiodj+buildbot
  2016-03-04 11:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 21:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82838bd626b10f1a82b0de29728c26f4458ec514 ***

Author: Cary Coutant <ccoutant@gmail.com>
Branch: master
Commit: 82838bd626b10f1a82b0de29728c26f4458ec514

Add new plugin hooks to support querying section alignment and size.

include/
2016-03-03  Than McIntosh <thanm@google.com>

	* plugin-api.h: Add new hooks to the plugin transfer vector to
	to support querying section alignment and section size.
	(ld_plugin_get_input_section_alignment): New hook.
	(ld_plugin_get_input_section_size): New hook.
	(ld_plugin_tag): Add LDPT_GET_INPUT_SECTION_ALIGNMENT
	and LDPT_GET_INPUT_SECTION_SIZE.
	(ld_plugin_tv): Add tv_get_input_section_alignment and
	tv_get_input_section_size.

gold/
2016-03-03  Than McIntosh  <thanm@google.com>

	* plugin.cc (Plugin::load): Include hooks for get_input_section_size
	and get_input_section_alignment in transfer vector.
	(get_input_section_alignment): New function.
	(get_input_section_size): New function.
	* testsuite/Makefile.am: Add plugin_layout_with_alignment.sh test.
	* testsuite/Makefile.in: [Regenerate.]
	* testsuite/plugin_section_alignment.cc: New test file.
	* testsuite/plugin_layout_with_alignment.cc: New test file.
	* testsuite/plugin_layout_with_alignment.sh: New test file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Treat common symbol in executable as definition
@ 2016-03-04 14:50 sergiodj+buildbot
  2016-03-04 16:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 14:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07492f668d2173da7a2bda3707ff0985e0f460b6 ***

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

Treat common symbol in executable as definition

Common symbol in executable is a definition, which overrides definition
from shared objects.  When linker sees a new definition from a shared
object, the new dynamic definition should be overridden by the previous
common symbol in executable.

bfd/

	PR ld/19579
	* elflink.c (_bfd_elf_merge_symbol): Treat common symbol in
	executable as definition if the new definition comes from a
	shared library.

ld/

	PR ld/19579
	* testsuite/ld-elf/pr19579a.c: New file.
	* testsuite/ld-elf/pr19579b.c: Likewise.
	* testsuite/ld-elf/shared.exp: Run PR ld/19579 test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add missing ChangeLog entries for commit 82838
@ 2016-03-04 16:41 sergiodj+buildbot
  2016-03-05 12:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f1f41f55f2fa5d390e57074477b6407302c8c46 ***

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

Add missing ChangeLog entries for commit 82838

Fix gold/testsuite/plugin_layout_with_alignment.sh permission.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Improve analysis of racy testcases
@ 2016-03-06  1:57 sergiodj+buildbot
  2016-03-06 22:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-06  1:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb6a751f5f1fe7912e84dd90d06395c357da47c2 ***

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

Improve analysis of racy testcases

This is an initial attempt to introduce some mechanisms to identify
racy testcases present in our testsuite.  As can be seen in previous
discussions, racy tests are really bothersome and cause our BuildBot
to pollute the gdb-testers mailing list with hundreds of
false-positives messages every month.  Hopefully, identifying these
racy tests in advance (and automatically) will contribute to the
reduction of noise traffic to gdb-testers, maybe to the point where we
will be able to send the failure messages directly to the authors of
the commits.

I spent some time trying to decide the best way to tackle this
problem, and decided that there is no silver bullet.  Racy tests are
tricky and it is difficult to catch them, so the best solution I could
find (for now?) is to run our testsuite a number of times in a row,
and then compare the results (i.e., the gdb.sum files generated during
each run).  The more times you run the tests, the more racy tests you
are likely to detect (at the expense of waiting longer and longer).
You can also run the tests in parallel, which makes things faster (and
contribute to catching more racy tests, because your machine will have
less resources for each test and some of them are likely to fail when
this happens).  I did some tests in my machine (8-core i7, 16GB RAM),
and running the whole GDB testsuite 5 times using -j6 took 23 minutes.
Not bad.

In order to run the racy test machinery, you need to specify the
RACY_ITER environment variable.  You will assign a number to this
variable, which represents the number of times you want to run the
tests.  So, for example, if you want to run the whole testsuite 3
times in parallel (using 2 cores), you will do:

  make check RACY_ITER=3 -j2

It is also possible to use the TESTS variable and specify which tests
you want to run:

  make check TEST='gdb.base/default.exp' RACY_ITER=3 -j2

And so on.  The output files will be put at the directory
gdb/testsuite/racy_outputs/.

After make invokes the necessary rules to run the tests, it finally
runs a Python script that will analyze the resulting gdb.sum files.
This Python script will read each file, and construct a series of sets
based on the results of the tests (one set for FAIL's, one for
PASS'es, one for KFAIL's, etc.).  It will then do some set operations
and come up with a list of unique, sorted testcases that are racy.
The algorithm behind this is:

  for state in PASS, FAIL, XFAIL, XPASS...; do
    if a test's state in every sumfile is $state; then
      it is not racy
    else
      it is racy

(The algorithm is actually a bit more complex than that, because it
takes into account other things in order to decide whether the test
should be ignored or not).

IOW, a test must have the same state in every sumfile.

After processing everything, the script prints the racy tests it could
identify on stdout.  I am redirecting this to a file named racy.sum.

Something else that I wasn't sure how to deal with was non-unique
messages in our testsuite.  I decided to do the same thing I do in our
BuildBot: include a unique identifier in the end of message, like:

  gdb.base/xyz.exp: non-unique message
  gdb.base/xyz.exp: non-unique message <<2>>

This means that you will have to be careful about them when you use
the racy.sum file.

I ran the script several times here, and it did a good job catching
some well-known racy tests.  Overall, I am satisfied with this
approach and I think it will be helpful to have it upstream'ed.  I
also intend to extend our BuildBot and create new, specialized
builders that will be responsible for detecting the racy tests every X
number of days.

2016-03-05  Sergio Durigan Junior  <sergiodj@redhat.com>

	* Makefile.in (DEFAULT_RACY_ITER): New variable.
	(CHECK_TARGET_TMP): Likewise.
	(check-single-racy): New rule.
	(check-parallel-racy): Likewise.
	(TEST_TARGETS): Adjust rule to account for RACY_ITER.
	(do-check-parallel-racy): New rule.
	(check-racy/%.exp): Likewise.
	* README (Racy testcases): New section.
	* analyze-racy-logs.py: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced
@ 2016-03-07 15:51 sergiodj+buildbot
  2016-03-07 18:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18f822a08fd5cb8fed8b0b318e7945545c255081 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 18f822a08fd5cb8fed8b0b318e7945545c255081

[AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced

2016-03-07  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (elfNN_aarch64_check_relocs): Always create .got section
  if the symbol "_GLOBAL_OFFSET_TABLE_" referenced.

ld/
  * testsuite/ld-aarch64/implicit_got_section_1.s: New test source file.
  * testsuite/ld-aarch64/implicit_got_section_1.d: New test expected result.
  * testsuite/ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix "set architecture mips:10000" crash
@ 2016-03-07 16:52 sergiodj+buildbot
  2016-03-07 20:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6c2f47b45315ba13f25fb57e51389d0c5ed0701 ***

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

Fix "set architecture mips:10000" crash

Fix this GDB crash:

  $ gdb -ex "set architecture mips:10000"
  Segmentation fault (core dumped)

Backtrace:

  Program received signal SIGSEGV, Segmentation fault.
  0x0000000000495b1b in mips_gdbarch_init (info=..., arches=0x0) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/mips-tdep.c:8436
  8436              if (bfd_get_flavour (info.abfd) == bfd_target_elf_flavour
  (top-gdb) bt
  #0  0x0000000000495b1b in mips_gdbarch_init (info=..., arches=0x0) at .../src/gdb/mips-tdep.c:8436
  #1  0x00000000007348a6 in gdbarch_find_by_info (info=...) at .../src/gdb/gdbarch.c:5155
  #2  0x000000000073563c in gdbarch_update_p (info=...) at .../src/gdb/arch-utils.c:522
  #3  0x0000000000735585 in set_architecture (ignore_args=0x0, from_tty=1, c=0x26bc870) at .../src/gdb/arch-utils.c:496
  #4  0x00000000005f29fd in do_sfunc (c=0x26bc870, args=0x0, from_tty=1) at .../src/gdb/cli/cli-decode.c:121
  #5  0x00000000005fd3f3 in do_set_command (arg=0x7fffffffdcdd "mips:10000", from_tty=1, c=0x26bc870) at .../src/gdb/cli/cli-setshow.c:455
  #6  0x0000000000836157 in execute_command (p=0x7fffffffdcdd "mips:10000", from_tty=1) at .../src/gdb/top.c:460
  #7  0x000000000071abfb in catch_command_errors (command=0x835f6b <execute_command>, arg=0x7fffffffdccc "set architecture mips:10000", from_tty=1)
      at .../src/gdb/main.c:368
  #8  0x000000000071bf4f in captured_main (data=0x7fffffffd750) at .../src/gdb/main.c:1132
  #9  0x0000000000716737 in catch_errors (func=0x71af44 <captured_main>, func_args=0x7fffffffd750, errstring=0x106b9a1 "", mask=RETURN_MASK_ALL)
      at .../src/gdb/exceptions.c:240
  #10 0x000000000071bfe6 in gdb_main (args=0x7fffffffd750) at .../src/gdb/main.c:1164
  #11 0x000000000040a6ad in main (argc=4, argv=0x7fffffffd858) at .../src/gdb/gdb.c:32
  (top-gdb)

We already check whether info.abfd is NULL before all other
bfd_get_flavour calls in the same function.  Just this one case was
missing.

(This was exposed by a WIP test that tries all "set architecture ARCH"
values.)

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

	* mips-tdep.c (mips_gdbarch_init): Check whether info.abfd is NULL
	before calling bfd_get_flavour.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Allow zero length archive elements.
@ 2016-03-07 17:40 sergiodj+buildbot
  2016-03-08 13:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fc874242f8f1bf17cf6e65b159dd804e793e6cd ***

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

Allow zero length archive elements.

bfd	PR binutils/19775
	* archive.c (bfd_generic_openr_next_archived_file): Allow zero
	length elements in the archive.

binutils PR binutils/19775
	* testsuite/binutils-all/ar.exp (proc empty_archive): New proc.
	Run the new proc.
	* testsuite/binutils-all/empty: New, empty, file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Assert that a floating type's length is at least as long as its format
@ 2016-03-09  3:19 sergiodj+buildbot
  2016-03-09  5:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  3:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b79497cb1cdc9b3053e5f0387bf3056c08c9bbdd ***

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

Assert that a floating type's length is at least as long as its format

This would have caught the HP/PA bug fixed in the previous patch:

 .../src/gdb/gdbtypes.c:4690: internal-error: arch_float_type: Assertion `len >= floatformat_totalsize_bytes (floatformats[0])' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)

Tested on x86-64 Fedora 23, --enable-targets=all.

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

	* doublest.c (floatformat_totalsize_bytes): New function.
	(floatformat_from_type): Assert that the type's length is at least
	as long as the floatformat's totalsize.
	* doublest.h (floatformat_totalsize_bytes): New declaration.
	* gdbtypes.c (arch_float_type): Assert that the type's length is
	at least as long as the floatformat's totalsize.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [CRIS] Don't internal error if forced big endian
@ 2016-03-09  3:39 sergiodj+buildbot
  2016-03-09  9:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  3:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 114d7832b0e07452277d748c81d8bc0c5675a1bc ***

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

[CRIS] Don't internal error if forced big endian

This fixes:

  $ ./gdb -q -ex "set endian big" -ex "set architecture cris"
  The target is assumed to be big endian
  .../src/gdb/cris-tdep.c:4051: internal-error: cris_gdbarch_init: big endian byte order in info
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n)

The "set cris-version" command can likewise cause internal errors.

The gdbarch init routine should be returning 0 to reject the
architecture instead of internal erroring on user input.

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

	* cris-tdep.c (cris_gdbarch_init): Return 0 if the info's byte
	order is BFD_ENDIAN_BIG or if the cris version is unsupported.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix floating conversion buffer overrun when host/target format matches
@ 2016-03-09  4:23 sergiodj+buildbot
  2016-03-09  7:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  4:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d7a87b5e4343467db23b70e73b156c9cc79c50ea ***

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

Fix floating conversion buffer overrun when host/target format matches

Running the testsuite with a gdb configured with --enable-libmcheck
reveals a problem:

  (gdb) ptype 3 * 2.0
  type = <12-byte float>
  memory clobbered past end of allocated block
  ERROR: Process no longer exists
  UNRESOLVED: gdb.ada/ptype_arith_binop.exp: ptype 3 * 2.0

  (gdb) PASS: gdb.dlang/expression.exp: ptype 0x1.FFFFFFFFFFFFFp1023
  ptype 0x1p-52L
  type = real
  memory clobbered past end of allocated block
  ERROR: Process no longer exists
  UNRESOLVED: gdb.dlang/expression.exp: ptype 0x1p-52L

Even though this shows up with Ada and D, it's easy to reproduce in C
too.  We just need to print a long double, when the current arch is
32-bit, which is the default when gdb starts up:

 $ ./gdb -q -ex "ptype 1.0L"
 type = long double
 memory clobbered past end of allocated block
 Aborted (core dumped)

Valgrind shows:

 ==22159== Invalid write of size 8
 ==22159==    at 0x8464A9: floatformat_from_doublest (doublest.c:756)
 ==22159==    by 0x846822: store_typed_floating (doublest.c:867)
 ==22159==    by 0x6A7959: value_from_double (value.c:3662)
 ==22159==    by 0x6A9F2D: evaluate_subexp_standard (eval.c:745)
 ==22159==    by 0x7F31AF: evaluate_subexp_c (c-lang.c:716)
 ==22159==    by 0x6A8986: evaluate_subexp (eval.c:79)
 ==22159==    by 0x6A8BA3: evaluate_type (eval.c:174)
 ==22159==    by 0x817CCF: whatis_exp (typeprint.c:456)
 ==22159==    by 0x817EAA: ptype_command (typeprint.c:508)
 ==22159==    by 0x5F267B: do_cfunc (cli-decode.c:105)
 ==22159==    by 0x5F5618: cmd_func (cli-decode.c:1885)
 ==22159==    by 0x83622A: execute_command (top.c:475)
 ==22159==  Address 0x8c6cb28 is 8 bytes inside a block of size 12 alloc'd
 ==22159==    at 0x4C2AA98: calloc (vg_replace_malloc.c:711)
 ==22159==    by 0x87384A: xcalloc (common-utils.c:83)
 ==22159==    by 0x873889: xzalloc (common-utils.c:93)
 ==22159==    by 0x6A34CB: allocate_value_contents (value.c:1036)
 ==22159==    by 0x6A3501: allocate_value (value.c:1047)
 ==22159==    by 0x6A790A: value_from_double (value.c:3656)
 ==22159==    by 0x6A9F2D: evaluate_subexp_standard (eval.c:745)
 ==22159==    by 0x7F31AF: evaluate_subexp_c (c-lang.c:716)
 ==22159==    by 0x6A8986: evaluate_subexp (eval.c:79)
 ==22159==    by 0x6A8BA3: evaluate_type (eval.c:174)
 ==22159==    by 0x817CCF: whatis_exp (typeprint.c:456)
 ==22159==    by 0x817EAA: ptype_command (typeprint.c:508)
 ==22159==
 type = long double
 (gdb)

Even if the target and host floating-point formats match, the length
of the types might still be different.  On x86, long double is the
80-bit extended precision type on both 32-bit and 64-bit ABIs, but by
default it is stored as 12 bytes on 32-bit, and 16 bytes on 64-bit,
for alignment reasons.  Several places in doublest.c already consider
this, but floatformat_to_doublest and floatformat_from_doublest miss
it.  E.g., convert_typed_floating and store_typed_floating,

Tested on x86-64 Fedora 23 with --enable-libmcheck, where it fixes the
crashed above.

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

	* doublest.c: Extend comments.
	(floatformat_to_doublest, floatformat_from_doublest): Copy the
	floatformat's total size, not the host type's size.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't create dynamic sections when relocatable
@ 2016-03-09  4:57 sergiodj+buildbot
  2016-03-09 11:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  4:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c1d7a087682074d585253ad38719ec2363eb2b7 ***

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

Don't create dynamic sections when relocatable

Since dynamic sections aren't applicable to relocatable file, don't
create dynamic sections for -E/--dynamic-list when relocatable.

bfd/

	PR ld/19789
	* elflink.c (elf_link_add_object_symbols): Create dynamic sections
	for -E/--dynamic-list only when not relocatable.

ld/

	PR ld/19789
	* testsuite/ld-elf/pr19789.d: New file.
	* testsuite/ld-elf/pr19789.s: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Allow zero length archive elements
@ 2016-03-09  6:37 sergiodj+buildbot
  2016-03-09 15:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  6:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03ee85837ec2e10f7b67c417b17ab3ffa97a98d2 ***

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

Allow zero length archive elements

	PR binutils/19775
	* coff-alpha.c (alpha_ecoff_openr_next_archived_file): Allow zero
	length elements in the archive.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [FR-V] Handle FR300
@ 2016-03-09 16:08 sergiodj+buildbot
  2016-03-09 20:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 087ccc6a4f8c754a4f4d31810839a631dbeabe0d ***

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

[FR-V] Handle FR300

Even though "set architecture" presents fr300 as option:

 (gdb) set architecture fr<TAB>
 fr300  fr400  fr450  fr500  fr550  frv

Actually selecting fr300 doesn't work:

 (gdb) set architecture fr300
 Architecture `fr300' not recognized.
 The target architecture is set automatically (currently i386)
 (gdb)

This just looks like an obvious oversight.  Looking around gcc and
binutils sources, FR300 is basically a FR500 specialized for DSP and
low power.

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

	* frv-tdep.c (frv_gdbarch_init): Handle bfd_mach_fr300.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Avoid spaces in osabi names
@ 2016-03-09 16:19 sergiodj+buildbot
  2016-03-09 22:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7990f1690e9ef0471634c871c790f6cf706866d ***

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

Avoid spaces in osabi names

It's not possible today to select some of the osabis by name.
Specifically, those that have spaces in their names and then the first
word is ambiguous...

For example:
 (gdb) set osabi <TAB>
 [...]
 FreeBSD ELF
 FreeBSD a.out
 [...]
 (gdb) set osabi FreeBSD ELF
 Ambiguous item "FreeBSD ELF".

In reality, because "set osabi" is an enum command, that was
equivalent to trying "set osabi FreeBSD", which is then obviously
ambiguous, because of "FreeBSD ELF" and "FreeBSD a.out".

Also, even if the first word is not ambiguous, we actually ignore
whatever comes after the first word:

 (gdb) set osabi GNU/Linux
 (gdb) show osabi
 The current OS ABI is "GNU/Linux".
 The default OS ABI is "GNU/Linux".
 (gdb) set osabi Windows SomeNonsense
                         ^^^^^^^^^^^^
 (gdb) show osabi
 The current OS ABI is "Windows CE".
 The default OS ABI is "GNU/Linux".
 (gdb)

Fix this by avoiding spaces in osabi names.

We could instead make "set osabi" have a custom set hook, or
alternatively make the enum set hook (in cli-setshow.c) handle values
with spaces, but OTOH, I have a feeling that could cause trouble.
E.g., in cases where we might want to write more than one enum value
in the same line.  We could support quoting as workaround, but, not
sure we want that.  "No spaces" seems like a simpler rule.

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

	* osabi.c (gdb_osabi_names): Avoid spaces in osabi names.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] S390: Add use of unavailable-stack frame ID
@ 2016-03-09 16:30 sergiodj+buildbot
  2016-03-09 23:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d53bec88f4c1576f74e918400aa2ccac2d129db ***

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

S390: Add use of unavailable-stack frame ID

When determining the frame ID of an inline frame, GDB currently asserts
that a valid ID of the underlying real frame is found, and that it does
not match outer_frame_id.  From inline_frame_this_id():

  /* For now, require we don't match outer_frame_id either (see
     comment above).  */
  gdb_assert (!frame_id_eq (*this_id, outer_frame_id));

However, this assertion may fail when the real frame's unwinder can not
determine the frame ID.  This happened on an s390x target with a binary
that lacked call frame information and also confused the prologue
analyzer, because then s390_frame_this_id() left the frame ID at its
default.

To fix this, this change enhances s390_frame_this_id such that an
unavailable-stack frame ID is built if no frame base can be determined
but the function address is available.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_prologue_frame_unwind_cache): Store
	frame func's PC in info->func before any other failure can occur.
	(s390_frame_this_id): Use frame_id_build_unavailable_stack if
	info->func has been filled out.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] S390: Recognize special jumps in prologue parser
@ 2016-03-09 16:41 sergiodj+buildbot
  2016-03-10  1:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc0e3f49c84055034cae31bba169100d107b28f4 ***

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

S390: Recognize special jumps in prologue parser

Functions compiled with the gcc option `-mhotpatch' may start with a
branch-never BRCL instruction as a 6-byte NOP.  And functions compiled
with `-mstack-size' contain a BRC instruction in their prologue that is
actually a conditional trap.  Both of these special jumps cause the
prologue parser to stop and yield bad unwinding results.

This change makes the prologue analyzer recognize such special jumps and
ignore them.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_analyze_prologue): Ignore BRC and BRCL
	instructions that do nothing or are conditional traps.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Add ax_pseudo_register_collect for powerpc.
@ 2016-03-09 18:02 sergiodj+buildbot
  2016-03-10  3:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 18:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a2fa07bd121498a492f84312a36629383fc9445 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 2a2fa07bd121498a492f84312a36629383fc9445

gdb: Add ax_pseudo_register_collect for powerpc.

gdb/ChangeLog:

	* rs6000-tdep.c (rs6000_ax_pseudo_register_collect): New function.
	(rs6000_gdbarch_init): Wire in the above.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Add gen_return_address for powerpc.
@ 2016-03-09 18:28 sergiodj+buildbot
  2016-03-10  4:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 18:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a67914defbe57290c714975d7c1ccefa787fd635 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: a67914defbe57290c714975d7c1ccefa787fd635

gdb: Add gen_return_address for powerpc.

gdb/ChangeLog:

	* rs6000-tdep.c: Add "ax.h" and "ax-gdb.h" includes.
	(rs6000_gen_return_address): New function.
	(rs6000_gdbarch_init): Wire in the above.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Eliminate async_annotation_suffix
@ 2016-03-09 20:15 sergiodj+buildbot
  2016-03-10 21:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 608ff013aae02e3ac4687691db57bbcb8984fe18 ***

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

Eliminate async_annotation_suffix

The comments and existence of this global are a bit of misleading
obfuscation, since this is only ever used to print the prompt
annotation, and never changes.  Just hardcode "prompt" where
necessary, as done for most other annotations.

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

	* event-top.c (async_annotation_suffix): Delete.
	(top_level_prompt, command_line_handler): Don't use
	'async_annotation_suffix' and simplify.
	* event-top.h (async_annotation_suffix): Delete declaration.
	(init_main): Remove reference to 'async_annotation_suffix'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Update prompt_for_continue comments
@ 2016-03-09 20:27 sergiodj+buildbot
  2016-03-10 23:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 720d2e96b424bb4bb1f7021f86763ff3df078e2b ***

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

Update prompt_for_continue comments

These comments are out of date -- we no longer call gdb_readline.  And
I think that mentioning the event loop is more useful here than
whatever GO32 issue had with gdb_readline, which may even no longer be
an issue.

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

	* utils.c (prompt_for_continue): Update comments.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use struct buffer in gdb_readline_no_editing
@ 2016-03-09 20:47 sergiodj+buildbot
  2016-03-11  3:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a3bde34bc61af108556c74b661533dadddcb178 ***

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

Use struct buffer in gdb_readline_no_editing

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

	* common/buffer.h (buffer_grow_char): New function.
	* top.c: Include buffer.h.
	(gdb_readline_no_editing): Rename 'prompt_arg' parameter to
	'prompt'.  Use struct buffer instead of xrealloc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Command line input handling TLC
@ 2016-03-09 21:19 sergiodj+buildbot
  2016-03-11  8:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b69d38afdea34e4fecab5ea47ffe1e594e0b6233 ***

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

Command line input handling TLC

I didn't manage to usefully split this further into smaller
independent pieces, so:

 - Use "struct buffer" more.

 - Split out the responsibility of composing a complete command line
   from multiple input lines split with backslash

    (
    E.g.:

       (gdb) print \
       1 + \
       2
       $1 = 3
       (gdb)
    )

   to a separate function.  Note we don't need the separate
   readline_input_state and more_to_come globals at all.  They were
   just obfuscating the logic.

 - Factor out the tricky mostly duplicated code in
   command_line_handler and command_line_input.

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

	* event-top.c (more_to_come): Delete.
	(struct readline_input_state): Delete.
	(readline_input_state): Delete.
	(get_command_line_buffer): New function.
	(command_handler): Update comments.  Don't handle NULL commands
	here.  Do not execute commented lines.
	(command_line_append_input_line): New function.
	(handle_line_of_input): New function, partly based on
	command_line_handler and command_line_input.
	(command_line_handler): Rewrite.
	* event-top.h (command_handler): New declaration.
	(command_loop): Defer command execution to command_handler.
	(command_line_input): Update comments.  Simplify, using struct
	buffer and handle_line_of_input.
	* top.h (struct buffer): New forward declaration.
	(handle_line_of_input): New declaration.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: fix doc string of target_can_use_hardware_watchpoint.
@ 2016-03-09 21:46 sergiodj+buildbot
  2016-03-11  9:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2343b78a778af9fe496c521bd49ba027cb8b48ae ***

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

gdb: fix doc string of target_can_use_hardware_watchpoint.

gdb/ChangeLog

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

	* target.h: Fix doc string of target_can_use_hardware_watchpoint.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Mark the i370 target as obsolete.
@ 2016-03-10 15:43 sergiodj+buildbot
  2016-03-11 13:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-10 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ed4ff97cbbeeb2658286769ac9e8a6a35390f26 ***

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

Mark the i370 target as obsolete.

	* config.bfd: Mark the i370 target as obsolete.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add $_as_string convenience function
@ 2016-03-10 22:34 sergiodj+buildbot
  2016-03-11 15:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-10 22:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2f3ccb9f81255fd1b4f877600f39979c2d7ece5 ***

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

Add $_as_string convenience function

This patch is a follow-up to "Add printf format specifier for printing
enumerator":

  https://sourceware.org/ml/gdb-patches/2016-02/msg00144.html

Instead of having a solution specific to the printf command, Pedro
suggested adding a general purpose function $_as_string() that would
cover this use case and more.

So, in order to print the textual label of an enum, one can use:

  (gdb) printf "Visiting node of type %s\n", $_as_string(node)
  Visiting node of type NODE_INTEGER

gdb/ChangeLog:

	* data-directory/Makefile.in (PYTHON_FILE_LIST): Install
	gdb/function/as_string.py.
	* python/lib/gdb/function/as_string.py: New file.
	* NEWS: Mention the new $_as_string function.

gdb/testsuite/ChangeLog:

	* gdb.python/py-as-string.exp: New file.
	* gdb.python/py-as-string.c: New file.

gdb/doc/ChangeLog:

	* gdb.texinfo (Convenience Functions): Document $_as_string.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb.base/default.exp: Add missing $_as_string to "show convenience" test
@ 2016-03-14 16:56 sergiodj+buildbot
  2016-03-14 18:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-14 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa4ff313317d6234bbd818b09332e7d85349a56a ***

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

gdb.base/default.exp: Add missing $_as_string to "show convenience" test

When adding the $_as_string convenience function, I missed a new test
failure in default.exp.  The tests lists the convenience functions, so
$_as_string should be added to the expected list.

Fixes:

+FAIL: gdb.base/default.exp: show convenience ($_caller_is = <internal function _caller_is> not found)

gdb/testsuite/ChangeLog:

	* gdb.base/default.exp: Add $_as_string to the list of expected
	convenience functions.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Regenerate bfd-in2.h
@ 2016-03-14 20:28 sergiodj+buildbot
  2016-03-15 11:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-14 20:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbe48798204180aa11c55e5377c1e23700b9c280 ***

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

Regenerate bfd-in2.h

	* bfd-in2.h: Regenerated.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions
@ 2016-03-16 16:29 sergiodj+buildbot
  2016-03-16 19:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc9333013723880949a1e07a3e04bdbc1a3c3032 ***

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

[ARM] Support ARMv8.2 FP16 simd instructions

gas/
	* config/tc-arm.c (N_S_32): New.
	(N_F_16_32): Likewise.
	(N_SUF_32): Support N_F16.
	(N_IF_32): Likewise.
	(neon_dyadic_misc): Likewise.
	(do_neon_cmp): Likewise.
	(do_neon_cmp_inv): Likewise.
	(do_neon_mul): Likewise.
	(do_neon_fcmp_absolute): Likewise.
	(do_neon_step): Likewise.
	(do_neon_abs_neg): Likewise.
	(CVT_FLAVOR_VAR): Likewise.
	(do_neon_cvt_1): Likewise.
	(do_neon_recip_est): Likewise.
	(do_vmaxnm): Likewise.
	(do_vrint_1): Likewise.
	(neon_check_type): Check architecture support for FP16 extension.
	(insns): Update comments.
	* testsuite/gas/arm/armv8-2-fp16-simd.s: New test source.
	* testsuite/gas/arm/armv8-2-fp16-simd.d: New testcase for arm mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-thumb.d: Likewise for thumb mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning.d: New rejection test for
	arm mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning-thumb.d: Likewise for
	thumb mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning.l: New expected rejection
	error file.

opcode/
	* arm-dis.c (neon_opcodes): Support new FP16 instructions.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] xml-tdesc.c (tdesc_start_enum): Fix c++ build.
@ 2016-03-16 17:48 sergiodj+buildbot
  2016-03-17 11:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfeeb14b8468ab3f60d719f2cde697d1b537eba8 ***

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

xml-tdesc.c (tdesc_start_enum): Fix c++ build.

gdb/ChangeLog:

	* xml-tdesc.c (tdesc_start_enum): Fix c++ build.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR remote/19496, interrupted syscall in forking-threads-plus-bkpt
@ 2016-03-16 22:29 sergiodj+buildbot
  2016-03-17 16:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 22:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7868401b7b63d851eea5de3b780591238d579bd1 ***

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

PR remote/19496, interrupted syscall in forking-threads-plus-bkpt

This patch addresses "fork:Interrupted system call" (or wait:) failures
in gdb.threads/forking-threads-plus-breakpoint.exp.

The test program spawns ten threads, each of which do ten fork/waitpid
sequences.  The cause of the problem was that when one of the fork
children exited before the corresponding fork parent could initiate its
waitpid for that child, a SIGCHLD and/or SIGSTOP was delivered and
interrupted a fork or waitpid in another thread.

The fix was to wrap the system calls in a loop to retry the call if
it was interrupted, like:

do
  {
    pid = fork ();
  }
while (pid == -1 && errno == EINTR);

Since this is a Linux-only test I figure it is OK to use errno and EINTR.
I tried a number of alternative fixes using SIG_IGN, SA_RESTART,
pthread_sigblock, and bsd_signal, but none of these worked as well.

Tested on Nios II Linux target with x86 Linux host.

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

	* gdb.threads/forking-threads-plus-breakpoint.c (thread_forks):
	Retry fork and waitpid on interrupted system call errors.
	* gdb.threads/forking-threads-plus-breakpoint.exp: (do_test):
	Use with_timeout_factor to increase timeout to 90.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] linux-record: Fix bad fall-through for pipe/pipe2
@ 2016-03-17  9:19 sergiodj+buildbot
  2016-03-17 22:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-17  9:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afdab9165435e17169b4984eeb29ea751319aa74 ***

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

linux-record: Fix bad fall-through for pipe/pipe2

This patch added handling for some syscalls to linux-record.c:

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

But for both `pipe' and `pipe2' the patch lacks a statement after an
`if', such that the following `break' is interpreted as the `if'-body
instead.

This adds the missing (return-) statements for the conditionals.

gdb/ChangeLog:

	* linux-record.c (record_linux_system_call): Add missing return
	statements to handling of pipe and pipe2 syscalls.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Make sparc_software_single_step static
@ 2016-03-18 15:45 sergiodj+buildbot
  2016-03-19  8:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c3f22346dd632201807c0718d5281ed1eea329f ***

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

Make sparc_software_single_step static

sparc_software_single_step is not used out of sparc-tdep.c, so this
patch makes it static.

gdb:

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

	* sparc-tdep.c (sparc_software_single_step): Make it static.
	* sparc-tdep.h (sparc_software_single_step): Remove declaration.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] ARM process record: median instructions
@ 2016-03-21 11:29 sergiodj+buildbot
  2016-03-21 16:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-21 11:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c55978a67a2e23999c3359a13bb807b665fcb33e ***

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

ARM process record: median instructions

This patch is to support some ARM median instructions in process
record.  With this patch applied, these fails are fixed:

 -FAIL: gdb.reverse/break-precsave.exp: run to end of main
 -FAIL: gdb.reverse/break-precsave.exp: go to end of main forward
 -FAIL: gdb.reverse/break-precsave.exp: end of record log
 -FAIL: gdb.reverse/break-reverse.exp: continue to breakpoint: end
 -FAIL: gdb.reverse/break-reverse.exp: end of record log
 -FAIL: gdb.reverse/until-precsave.exp: run to end of main
 -FAIL: gdb.reverse/until-precsave.exp: advance to marker2
 -FAIL: gdb.reverse/until-precsave.exp: until func, not called by current frame
 -FAIL: gdb.reverse/until-precsave.exp: reverse-advance to marker2
 -FAIL: gdb.reverse/until-precsave.exp: reverse-finish from marker2
 -FAIL: gdb.reverse/until-precsave.exp: reverse-advance to final return of factorial
 -FAIL: gdb.reverse/until-precsave.exp: reverse-until to entry of factorial
 -FAIL: gdb.reverse/until-reverse.exp: advance to marker2
 -FAIL: gdb.reverse/until-reverse.exp: until func, not called by current frame
 -FAIL: gdb.reverse/until-reverse.exp: reverse-advance to marker2
 -FAIL: gdb.reverse/until-reverse.exp: reverse-finish from marker2
 -FAIL: gdb.reverse/until-reverse.exp: reverse-advance to final return of factorial
 -FAIL: gdb.reverse/until-reverse.exp: reverse-until to entry of factorial

gdb:

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

	* arm-tdep.c (arm_record_media): New.
	(arm_record_ld_st_reg_offset): Call arm_record_media.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Tidy up AArch64 simulator code.
@ 2016-03-29 10:50 sergiodj+buildbot
  2016-03-29 13:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-29 10:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef0d8ffc45aa32ed1e49051a344fa6c8cff583f4 ***

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

Tidy up AArch64 simulator code.

	* cpustate.c: Remove space after asterisk in function parameters.
	* decode.h (greg): Delete unused function.
	(vreg, shift, extension, scaling, writeback, condcode): Likewise.
	* simulator.c: Use INSTR macro in more places.
	(HALT_NYI): Use sim_io_eprintf in place of fprintf.
	Remove extraneous whitespace.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbserver/s390: Switch on tracepoint support.
@ 2016-03-29 21:56 sergiodj+buildbot
  2016-03-29 23:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-29 21:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a4105d04e19efdf89d0fa56b62675d7d7ee82a9b ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: a4105d04e19efdf89d0fa56b62675d7d7ee82a9b

gdbserver/s390: Switch on tracepoint support.

Also adds s390 support to gdb.trace testsuite.

gdb/gdbserver/ChangeLog:

	* linux-s390-low.c (s390_supports_tracepoints): New function.
	(struct linux_target_ops): Fill supports_tracepoints hook.

gdb/testsuite/ChangeLog:

	* gdb.trace/ftrace.exp: Set arg0exp for s390.
	* gdb.trace/mi-trace-frame-collected.exp: Expect 4 registers on s390.
	* gdb.trace/mi-trace-unavailable.exp: Set pcnum for s390, add gpr0num
	variable for GPR 0 instead of assuming it is register 0.
	* gdb.trace/trace-common.h: Add s390 fast tracepoint placeholder.
	* lib/trace-support.exp: Add s390 registers.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix a seg-fault in the AVR linker.
@ 2016-03-30 14:16 sergiodj+buildbot
  2016-03-30 15:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-30 14:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 024ea11b48d2270cd0b3b2b6fbe9e42c9fd232e0 ***

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

Fix a seg-fault in the AVR linker.

	* elf32-avr.c (avr_elf32_load_records_from_section): Free
	internal_relocs only if they aren't cached.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] enable -Wwrite-strings for gas
@ 2016-03-31 11:40 sergiodj+buildbot
  2016-03-31 13:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 11:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6757cf57697d30c73f4e3f314883ad2d8999eac6 ***

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

enable -Wwrite-strings for gas

We add a new AC_SUBST to warning.m4 so that the test if the warning is
supported is centralized, but the warning can be enabled per directory.

binutils/ChangeLog:

2016-03-31  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* configure: Regenerate.

gprof/ChangeLog:

2016-03-31  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* configure: Regenerate.

ld/ChangeLog:

2016-03-31  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* configure: Regenerate.

opcodes/ChangeLog:

2016-03-31  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* configure: Regenerate.

bfd/ChangeLog:

2016-03-31  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* configure: Regenerate.
	* warning.m4: Add WARN_WRITE_STRINGS AC_SUBST.

gold/ChangeLog:

2016-03-31  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* configure: Regenerate.

gas/ChangeLog:

2016-03-31  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* Makefile.am: Add WARN_WRITE_STRINGS to WARN_CFLAGS.
	* Makefile.in: Regenerate.
	* configure: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] python: Use console format for output of gdb.execute command
@ 2016-03-31 12:58 sergiodj+buildbot
  2016-03-31 16:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 12:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7ea3ec7c623be0b9be1eaf4929794652a84be11 ***

Author: Catalin Udma <catalin.udma@freescale.com>
Branch: master
Commit: e7ea3ec7c623be0b9be1eaf4929794652a84be11

python: Use console format for output of gdb.execute command

When gdb is started in MI mode, the output of gdb.execute
command is in MI-format in case when it is executed from python stop
handler while for all other cases the output is in console-format.

To assure consistent output format, this is fixed by using the console
format for all python gdb command executions.

PR python/19743

gdb/ChangeLog:
2016-03-31  Catalin Udma  <catalin.udma@freescale.com>

	PR python/19743
	* python/python.c (execute_gdb_command): Use console uiout
	when executing gdb command.
	* utils.c (restore_ui_out_closure): New structure.
	(do_restore_ui_out): New function.
	(make_cleanup_restore_ui_out): Likewise.
	* utils.h (make_cleanup_restore_ui_out): Declare.

gdb/testsuite/ChangeLog:
2016-03-31  Catalin Udma  <catalin.udma@freescale.com>

	PR python/19743
	* gdb.python/py-mi-events-gdb.py: New file.
	* gdb.python/py-mi-events.c: New file.
	* gdb.python/py-mi-events.exp: New file.

Signed-off-by: Catalin Udma <catalin.udma@freescale.com>


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Improve gdb_remote_download, remove gdb_download
@ 2016-04-05 18:35 sergiodj+buildbot
  2016-04-06  5:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 18:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7817ea46148df2931cf00d17aeedb844b6e4e4db ***

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

Improve gdb_remote_download, remove gdb_download

This patch removes gdb_download in favor of gdb_remote_download, since
they are very close in functionality.  Also, in preparation for the
following patch about shared library handling during tests, it improves
gdb_remote_download so that it uses standard_output_file for any
destination board that is local, not only host.

If the destination board is remote, gdb_remote_download will use the
standard remote_download from DejaGnu, resulting in the file being
transferred on the remote system.

If the destination is local, gdb_remote_download will copy the file to
the standard test directory (found using standard_output_file).  Tcl's
file copy seems to handle gracefully cases where the source file is the
same as the destination, so I don't think it's necessary to check for
that case ourselves, as a previous version of the patch did.

I'd prefer to keep the name gdb_download instead of gdb_remote_download,
since I don't like the fact that gdb_remote_download implies that the
destination is remote, when it's not always the case.  However,
gdb_remote_download is used at many more places than gdb_download, so
it's easier to reuse that.  Also, since it's a wrapper around DejaGnu's
remote_download, it might be better to keep that name.  I don't know.

I ran the testsuite native, with native-gdbserver and with a
remote gdbserver, and didn't see any related failure.

gdb/testsuite/ChangeLog:

	* gdb.base/jit-so.exp: Use gdb_remote_download instead of
	gdb_download.  Use it even if the target is not remote.
	* gdb.base/jit.exp (compile_jit_test): Likewise.
	* lib/gdb.exp (gdb_remote_download): Copy files to the standard
	output directory if the destination board is local, otherwise use
	the standard remote_download from DejaGnu.
	(gdb_download): Remove.
	(gdb_load_shlibs): Use gdb_remote_download instead of
	gdb_download.
	* lib/gdbserver-support.exp (gdbserver_download_current_prog):
	Use gdb_remote_download instead of gdb_download.  Use it even if
	the target is not remote.
	* lib/mi-support.exp (mi_load_shlibs): Use gdb_remote_download
	instead of gdb_download.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Make ftrace tests work with remote targets
@ 2016-04-05 19:25 sergiodj+buildbot
  2016-04-06  7:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e774b13c3b81ac2599812adf058796948ce7e95 ***

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

Make ftrace tests work with remote targets

When we build a shared library for testing, it is built differently
whether it is meant for the local system or a remote one.  When it is
for the local system, the library is built with no SONAME.  So when the
executable is built, roughly in this way:

  $ gcc testfile.c /path/to/library.so

the executable will contain an absolute reference to the library.  For
example:

  $ readelf -a testsuite/gdb.python/py-shared | grep NEEDED
   0x0000000000000001 (NEEDED)             Shared library: [/home/emaisin/build/binutils-gdb/gdb/testsuite/gdb.python/py-shared-sl.sl]

When testing is done remotely, the absolute path obviously doesn't work.
Therefore, we build the library with an SONAME:

  $ readelf -a testsuite/gdb.python/py-shared-sl.sl | grep SONAME
   0x000000000000000e (SONAME)             Library soname: [py-shared-sl.sl]

which ends up in the executable's NEEDED field:

  $ readelf -a testsuite/gdb.python/py-shared | grep NEEDED
   0x0000000000000001 (NEEDED)             Shared library: [py-shared-sl.sl]

The executable and the library are then uploaded side-by-side on the
remote system.  To allow the dynamic linker to find the shared library,
we have to add the special RPATH value $ORIGIN, which tells it to search
in the executable's directory:

  $ readelf -a testsuite/gdb.python/py-shared | grep ORIGIN
   0x000000000000000f (RPATH)              Library rpath: [$ORIGIN]

The problem with the IPA library is that it doesn't have an SONAME,
making it very difficult to do testing on a remote board.  When a
test executable is linked with it, it contains an absolute reference to
the library path.  Therefore, unless the paths on the target are the
same as on the build system, it won't work.

To make it possible for tests using the IPA library to run test on
remote boards, I suggest adding an SONAME to libinproctrace.so.  I don't
think it should be a big problem for users.  All the libraries installed
on my system have an SONAME, so it should be fine if libinproctrace.so
does too.

As a consequence, native testing does not work anymore, since
executables do not contain the absolute path to the library anymore.  To
keep them working, we can have gdb_load_shlibs copy the library to the
test directory when testing natively.  That's done by modifying
gdb_load_shlibs.  We also have to add RPATH=$ORIGIN to executables, even
when testing natively.

I think it's a good change in general, as it reduces the differences
between testing a native and a remote target.  To further reduce those
differences, we can also always build test shared libraries with an
SONAME.

ftrace.exp and ftrace-lock.exp need to be modified slightly.  The code
checks that the IPA library is loaded using the absolute path on the
build machine.  That obviously doesn't work if the test is done
remotely, as the path will be different.  I changed the tests to only
search for the library basename (e.g. libinproctrace.so).

gdb/gdbserver/ChangeLog:

	* Makefile.in ($(IPA_LIB)): Set SONAME of the IPA lib.

gdb/testsuite/ChangeLog:

	* gdb.trace/ftrace-lock.exp: Check for IPA basename instead of
	absolute.
	* gdb.trace/ftrace.exp: Likewise.
	* lib/gdb.exp (gdb_compile): Set rpath $ORIGIN for non-remote
	targets as well.
	(gdb_compile_shlib): Set SONAME for non-remote targets as well.
	(gdb_load_shlibs): Copy libraries to test directory when testing
	natively.  Only set solib-search-path if testing remotely.
	* lib/mi-support.exp (mi_load_shlibs): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc/nps400: Add additional instructions
@ 2016-04-05 22:02 sergiodj+buildbot
  2016-04-06  9:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 22:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 820f03ffe027367f275e9debb5f3f3376820ab37 ***

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

arc/nps400: Add additional instructions

Adds the movbi, decode1, fbset, fbclear, encode0, encode1, rflt, crc16,
and crc32 instructions for the nps400 arc machine type.

gas/ChangeLog:

	* testsuite/gas/arc/nps400-1.d: Update expected results.
	* testsuite/gas/arc/nps400-1.s: Additional test cases.

opcodes/ChangeLog:

	* arc-nps400-tbl.h: Add movbi, decode1, fbset, fbclear, encode0,
	encode1, rflt, crc16, and crc32 instructions.
	* arc-opc.c (arc_flag_operands): Add F_NPS_R.
	(arc_flag_classes): Add C_NPS_R.
	(insert_nps_bitop_size_2b): New function.
	(extract_nps_bitop_size_2b): Likewise.
	(insert_nps_bitop_uimm8): Likewise.
	(extract_nps_bitop_uimm8): Likewise.
	(arc_operands): Add new operand entries.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix IPA detection in ftrace-insn-reloc.exp
@ 2016-04-06  1:00 sergiodj+buildbot
  2016-04-06 10:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-06  1:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03a8c4dfc295fdebf4dac7a5ee91592e69b404a6 ***

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

Fix IPA detection in ftrace-insn-reloc.exp

In commit 6e774b13c3b, I forgot to update this test.

gdb/testsuite/ChangeLog:

	* gdb.arch/ftrace-insn-reloc.exp: Check for IPA basename instead of
	absolute.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Update py-mi-objfile to expect console format print
@ 2016-04-06  7:08 sergiodj+buildbot
  2016-04-06 12:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-06  7:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac17fda08bf2a75ba561a919f05df95ff07959de ***

Author: Catalin Udma <catalin.udma@freescale.com>
Branch: master
Commit: ac17fda08bf2a75ba561a919f05df95ff07959de

testsuite: Update py-mi-objfile to expect console format print

Starting with this commit:

  commit e7ea3ec7c623be0b9be1eaf4929794652a84be11
  Author: Catalin Udma <catalin.udma@freescale.com>
  Date:   Mon Feb 29 16:16:19 2016 +0200

    python: Use console format for output of gdb.execute command

the python script would use console format for gdb.execute output.
This patch fixes py-mi-objfile to expect the console format when is
checking for gdb.execute printing.

gdb/testsuite/ChangeLog:
2016-04-05  Catalin Udma  <catalin.udma@freescale.com>

        * gdb.python/py-mi-objfile-gdb.py: Use "list main" command.
        * gdb.python/py-mi-objfile.exp: Match "list main" output
        in console format.

Signed-off-by: Catalin Udma <catalin.udma@freescale.com>


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdb.threads/dlopen-libpthread.exp crash
@ 2016-04-06 21:04 sergiodj+buildbot
  2016-04-07  0:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-06 21:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2f901dfb6cb5ae2845a48503df1fe0065085f83 ***

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

Fix gdb.threads/dlopen-libpthread.exp crash

Following, commit

  6e774b13c3b81ac2599812adf058796948ce7e95 Make ftrace tests work with remote targets

the test gdb.threads/dlopen-libpthread.exp started to fail with:

  ERROR: error copying "/home/emaisin/build/binutils-gdb/gdb/testsuite/gdb.threads/dlopen-libpthread.so": no such file or directory

This is because the library path is not computed using
standard_output_file, so we try to gdb_load_shlibs an unexisting file.

gdb/testsuite/ChangeLog:

	* gdb.threads/dlopen-libpthread.exp: Set binfile_lib using
	standard_output_file.  Remove unused binfile variable.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Optimized-out pointer: New test for error handling
@ 2016-04-06 21:44 sergiodj+buildbot
  2016-04-07  1:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-06 21:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b16f8a3b1ecce592fe331a5b1ce6632951350e9c ***

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

Optimized-out pointer: New test for error handling

This patch implements a test that ensures that with "set print object
on", -var-create returns "<optimized out>" for an optimized out pointer
to structure, rather than throwing an error, while also ensuring that
any attempt to dereference the pointer *will* throw an error.

It uses the dwarf assembler to construct the appropriate debug info
to represent a pointer-to-struct in the program as optimized out,
and then accesses that pointer in various ways.  The test uses both
the console interpreter and the MI interpreter.

gdb/testsuite/ChangeLog:
2016-04-06  Don Breazeal  <donb@codesourcery.com>

	* gdb.dwarf2/dw2-opt-structptr.c: New test program.
	* gdb.dwarf2/dw2-opt-structptr.exp: New test script.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Make breakpoint handling in record-full idempotent
@ 2016-04-07 16:30 sergiodj+buildbot
  2016-04-07 19:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-07 16:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e390720bdc6ddee752992537259d18d1ae8d2eb1 ***

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

Make breakpoint handling in record-full idempotent

Some test fails in gdb.reverse/break-reverse.exp on arm-linux lead me
seeing the following error message,

continue^M
Continuing.^M
Cannot remove breakpoints because program is no longer writable.^M
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Further execution is probably impossible.^M
^M
Breakpoint 3, bar () at /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.reverse/break-reverse.c:22^M
22        xyz = 2; /* break in bar */^M
(gdb) PASS: gdb.reverse/break-reverse.exp: continue to breakpoint: bar backward

this is caused by two entries in record_full_breakpoints, and their addr
is the same, but in_target_beneath is different.

during the record, we do continue,

Continuing.
infrun: clear_proceed_status_thread (Thread 13772.13772)
infrun: proceed (addr=0xffffffff, signal=GDB_SIGNAL_DEFAULT)
infrun: step-over queue now empty
infrun: resuming [Thread 13772.13772] for step-over
infrun: skipping breakpoint: stepping past insn at: 0x8620
Sending packet: $Z0,85f4,4#1d...Packet received: OK  <----
.....
Sending packet: $vCont;c#a8...infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [process -1],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [process -1],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
Packet received: T05swbreak:;0b:9cf5ffbe;0d:9cf5ffbe;0f:f4850000;thread:p35cc.35cc;core:1;
Sending packet: $Z0,85f4,4#1d...Packet received: OK <-----
....
Sending packet: $z0,85f4,4#3d...Packet received: OK <-----

we can see breakpoint on 0x85f4 are inserted *twice*, but only removed
once.  That is fine to remote target, because Z/z packets are
idempotent, but there is a leftover in record_full_breakpoints
in record-full target.  The flow can be described as below,

                                record_full_breakpoints   remote target
  -----------------------------------------------------------------------
  forward execution, continue,    in_target_beneath 1     breakpoint inserted
  insert breakpoints on 0x85f4    in_target_beneath 1
  twice

  program stops,
  remove breakpoint on 0x85f4     in_target_beneath 1     breakpoint removed

  reverse execution, continue,    in_target_beneath 1     none is requested
  insert breakpoints on 0x85f4,   in_target_beneath 0

  program stops,
  remote breakpoint on 0x85f4,    in_target_beneath 0     request to remove,
                                                          but GDBserver
							  doesn't know

now, the question is why breakoint on 0x85f4 is inserted twice?  One
is the normal breakpoint, and the other is the single step breakpoint.
GDB inserts single step breakpoint to do single step.  When program
stops at 0x85f4, both of them are set on 0x85f4, and GDB deletes
single step breakpoint, so in update_global_location_list, this
breakpoint location is no longer found, GDB call
force_breakpoint_reinsertion to mark it condition_updated, and insert
it again.

The reason force_breakpoint_reinsertion is called to update the
conditions in the target side, because the conditions may be
changed.  My original fix is to not call force_breakpoint_reinsertion
if OLD_LOC->cond is NULL, but it is not correct if another location
on the same address has condition, GDB doesn't produce condition for
target side, but GDB should do.

Then, I change my mind back to make record-full handling breakpoint
idempotent, to align with remote target.  Before insert a new entry
into record_full_breakpoints, look for existing one on the same
address first.  I also add an assert on
"bp->in_target_beneath == in_target_beneath", to be safer.

gdb:

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

	* record-full.c (record_full_insert_breakpoint): Return
	early if entry on the address is found in
	record_full_breakpoints.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdb.reverse/finish-reverse-bkpt.exp
@ 2016-04-07 17:21 sergiodj+buildbot
  2016-04-07 22:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-07 17:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8064e7e9b4d7d9cc29a613af899a7739df60be6 ***

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

Fix gdb.reverse/finish-reverse-bkpt.exp

I see the following fail on aarch64-linux

 break void_func
 Breakpoint 2 at 0x4007a0: file gdb/testsuite/gdb.reverse/finish-reverse.c, line 44.
 (gdb) PASS: gdb.reverse/finish-reverse-bkpt.exp: set breakpoint on void_func
 continue
 Continuing.

 Breakpoint 2, void_func () at gdb/testsuite/gdb.reverse/finish-reverse.c:44^M
 44        void_test = 1;                /* VOID FUNC */^M
 (gdb) PASS: gdb.reverse/finish-reverse-bkpt.exp: continue to breakpoint: void_func
 break *void_func^M
 Note: breakpoint 2 also set at pc 0x4007a0.^M
 Breakpoint 3 at 0x4007a0: file gdb/testsuite/gdb.reverse/finish-reverse.c, line 44.
 (gdb) PASS: gdb.reverse/finish-reverse-bkpt.exp: set breakpoint at void_func's entry
 reverse-finish^M
 Run back to call of #0  void_func () at gdb/testsuite/gdb.reverse/finish-reverse.c:44
 main (argc=1, argv=0x7ffffffb78) at gdb/testsuite/gdb.reverse/finish-reverse.c:98
 98        void_func ();                                 /* call to void_func */^M
 (gdb) FAIL: gdb.reverse/finish-reverse-bkpt.exp: reverse-finish from void_func trips breakpoint at entry

The test assumes that brekapoints on "void_func" and "*void_func" are
set on different places because of function prologue.  However, on
aarch64-linux, there is no prologue in void_func, so two breakpoints
are set at the same place (0x4007a0).

(gdb) disassemble void_func
Dump of assembler code for function void_func:
   0x00000000004007a0 <+0>:	adrp	x0, 0x410000
   0x00000000004007a4 <+4>:	add	x0, x0, #0xc14
   0x00000000004007a8 <+8>:	mov	w1, #0x1
   0x00000000004007ac <+12>:	str	w1, [x0]
   0x00000000004007b0 <+16>:	ret

The fix to this problem is to single step forward before setting
breakpoint on *void_func.

gdb/testsuite:

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

	* gdb.reverse/finish-reverse-bkpt.exp: Use temporary breakpoint.
	Execute "si" command.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gas/arc: Handle multiple arc_opcode chains for same mnemonic
@ 2016-04-07 17:52 sergiodj+buildbot
  2016-04-08  0:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-07 17:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1328504b287b2c284419d989e0d05e7d6d3ffa59 ***

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

gas/arc: Handle multiple arc_opcode chains for same mnemonic

This commit completes support for having multiple instructions with the
same mnemonic in non-contiguous blocks within the arc_opcodes table.

The commit adds an iterator mechanism for the arc_opcode_hash_entry
structure, which is then used in find_opcode_match to consider all
arc_opcode entries with the same mnemonic, even when these instructions
are stored in non-contiguous blocks.

I extend the comment on the arc_opcodes table to discuss how entries
within the table are organised, and to mention how instructions can be
split into multiple groups if needed, but that the table is still
searched in table order.

There should be no user visible changes after this commit.

gas/ChangeLog:

	* config/tc-arc.c (struct arc_opcode_hash_entry_iterator): New
	structure.
	(arc_opcode_hash_entry_iterator_init): New function.
	(arc_opcode_hash_entry_iterator_next): New function.
	(find_opcode_match): Iterate over all arc_opcode entries
	referenced by the arc_opcode_hash_entry passed in as a parameter.

opcodes/ChangeLog:

	* arc-opc.c (arc_opcodes): Extend comment to discus table layout.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc/nps400: Add new instructions
@ 2016-04-07 18:15 sergiodj+buildbot
  2016-04-08  2:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-07 18:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a42a4f8400ee232ceed5ecceb61873195984f1d9 ***

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

arc/nps400: Add new instructions

Add some new control instructions to the opcodes library, and a new test
for these new instructions to the assembler.  The new instructions use
an instruction flag longer than any seen before (on arc), and so the max
flag length is extended to accommodate this.

gas/ChangeLog:

	* config/tc-arc.h (MAX_FLAG_NAME_LENGTH): Increase to 7.
	* testsuite/gas/arc/nps400-2.d: New file.
	* testsuite/gas/arc/nps400-2.s: New file.

opcodes/ChangeLog:

	* arc-nps400-tbl.h: Add schd, sync, and hwschd instructions.
	* arc-opc.c (arc_flag_operands): Add new flags.
	(arc_flag_classes): Add new classes.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdb.compile/compile.exp shlib regression
@ 2016-04-07 19:12 sergiodj+buildbot
  2016-04-08  3:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-07 19:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9553661a5f8fb5f82846a04a02b7db8476d986e0 ***

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

Fix gdb.compile/compile.exp shlib regression

Commit 6e774b13c3b8 (Make ftrace tests work with remote targets) made
a few gdb.compile/compile.exp tests disappear:

 -PASS: gdb.compile/compile.exp: call shared library function
 -PASS: gdb.compile/compile.exp: expect 1
 -PASS: gdb.compile/compile.exp: modify shared library variable
 -PASS: gdb.compile/compile.exp: expect 15

This is because the test uses ldflags instead of using the shlib
option, so it misses linking with -rpath, resulting in:

 (gdb) run
 Starting program: .../compile/compile-shlib
 .../compile/compile-shlib: error while loading shared libraries: compile-shlib.so: cannot open shared object file: No such file or directory
 [Inferior 1 (process 18014) exited with code 0177]

We were missing a gdb_load_shlibs call, which is needed for remote
testing.

gdb/testsuite/ChangeLog:
2015-04-07  Pedro Alves  <palves@redhat.com>

	* gdb.compile/compile.exp: Use gdb_compile with "shlib=" option
	instead of build_executable.  Use gdb_load_shlibs.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for .extCondCode, .extCoreRegister and .extAuxRegister.
@ 2016-04-12 10:00 sergiodj+buildbot
  2016-04-13  0:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 10:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f36e33dac1a97cca8f79ca8b20cf0fb05f1e25f4 ***

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

Add support for .extCondCode, .extCoreRegister and .extAuxRegister.

gas/
2016-04-05  Claudiu Zissulescu  <claziss@synopsys.com>

	* testsuite/gas/arc/textauxregister.d: New file.
	* testsuite/gas/arc/textauxregister.s: Likewise.
	* testsuite/gas/arc/textcondcode.d: Likewise.
	* testsuite/gas/arc/textcondcode.s: Likewise.
	* testsuite/gas/arc/textcoreregister.d: Likewise.
	* testsuite/gas/arc/textcoreregister.s: Likewise.
	* testsuite/gas/arc/textpseudoop.d: Likewise.
	* testsuite/gas/arc/textpseudoop.s: Likewise.
	* testsuite/gas/arc/ld2.d: Update test.
	* testsuite/gas/arc/st.d: Likewise.
	* testsuite/gas/arc/taux.d: Likewise.
	* doc/c-arc.texi (ARC Directives): Add .extCondCode,
	.extCoreRegister and .extAuxRegister documentation.
	* config/tc-arc.c (arc_extcorereg): New function.
	(md_pseudo_table): Add .extCondCode, .extCoreRegister and
	.extAuxRegister pseudo-ops.
	(extRegister_t): New type.
	(ext_condcode, arc_aux_hash): New global variable.
	(find_opcode_match): Check for extensions.
	(preprocess_operands): Likewise.
	(md_begin): Add aux registers in a hash.
	(assemble_insn): Update use arc_flags member.
	(tokenize_extregister): New function.
	(create_extcore_section): Likewise.
	* config/tc-arc.h (MAX_FLAG_NAME_LENGHT): Increase to 10.
	(arc_flags): Delete code, add flgp.

include/
2016-04-05  Claudiu Zissulescu  <claziss@synopsys.com>

	* opcode/arc.h (flag_class_t): Update.
	(ARC_OPCODE_NONE): Define.
	(ARC_OPCODE_ARCALL): Likewise.
	(ARC_OPCODE_ARCFPX): Likewise.
	(ARC_REGISTER_READONLY): Likewise.
	(ARC_REGISTER_WRITEONLY): Likewise.
	(ARC_REGISTER_NOSHORT_CUT): Likewise.
	(arc_aux_reg): Add cpu.

opcodes/
2016-04-05  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-dis.c (find_format): Check for extension flags.
	(print_flags): New function.
	(print_insn_arc): Update for .extCondCode, .extCoreRegister and
	.extAuxRegister.
	* arc-ext.c (arcExtMap_coreRegName): Use
	LAST_EXTENSION_CORE_REGISTER.
	(arcExtMap_coreReadWrite): Likewise.
	(dump_ARC_extmap): Update printing.
	* arc-opc.c (arc_flag_classes): Add F_CLASS_EXTEND flag.
	(arc_aux_regs): Add cpu field.
	* arc-regs.h: Add cpu field, lower case name aux registers.

Signed-off-by: Claudiu Zissulescu <claziss@synopsys.com>


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

*** TEST RESULTS FOR COMMIT c5ac15402a894e87a118526a066880f596b3c78d ***

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

Use target_terminal_ours_for_output in warning/internal_error

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

And restore terminal settings, while at it.

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

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


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

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

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

Do target_terminal_ours in query & friends instead of in all callers

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

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

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

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

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

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


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

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

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

gdb/ada-exp.y: Remap yydefred

On:

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

The link fails with:

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

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

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

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


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

*** TEST RESULTS FOR COMMIT d04c1a59f3b6ae23f16988961cd74b561ed6f8d6 ***

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

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

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Build GDB as a C++ program by default
@ 2016-04-20 22:27 sergiodj+buildbot
  2016-04-21 16:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 22:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a23585089d7ba710b238d3d1ab3d34320afa48d0 ***

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

Build GDB as a C++ program by default

This makes --enable-build-with-cxx be "yes" by default.

One must now configure with --enable-build-with-cxx=no in order to
build with a C compiler.

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

	* build-with-cxx.m4 (GDB_AC_BUILD_WITH_CXX): Default to yes.
	* configure: Renegerate.

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

	* configure: Renegerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't check relocations in excluded sections
@ 2016-04-21  0:21 sergiodj+buildbot
  2016-04-21 19:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-21  0:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ce03cea78d4d8bf00e29e4dfa4952d53f3b1064 ***

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

Don't check relocations in excluded sections

When checking relocations after gc-sections has run, the unused sections
have been removed.  Don't check relocations in excluded sections.

	* elflink.c (_bfd_elf_link_check_relocs): Don't check relocations
	in excluded sections


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove x86 gc_sweep_hook
@ 2016-04-21  0:25 sergiodj+buildbot
  2016-04-21 23:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-04-21  0:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e66cdd681f47dc51beaeee3d813f1c9cba27dedf ***

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

Remove x86 gc_sweep_hook

Since x86 backends never see the removed sections, there is no need
for gc_sweep_hook.

	* elf32-i386.c (elf_i386_gc_sweep_hook): Removed.
	(elf_backend_gc_sweep_hook): Likewise.
	* elf64-x86-64.c (elf_x86_64_gc_sweep_hook): Likewise.
	(elf_backend_gc_sweep_hook): Likewise.


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

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

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

Fix AIX gdb build with C++ compiler

We currently get:

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


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


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

(and more instances of the same).

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

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


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

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

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

Switch gdb's TRY/CATCH to sjlj again

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

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

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

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

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


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

*** TEST RESULTS FOR COMMIT e62b9723fdfcf655ecbd46ea455567593e333f47 ***

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

Pass GOT_RELOC to UNDEFINED_WEAK_RESOLVED_TO_ZERO

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

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


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

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

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

[AArch64] Also puts value in place for R_AARCH64_RELATIVE

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

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdb/python/python.c use-after-free
@ 2016-05-03 12:30 sergiodj+buildbot
  2016-05-04  1:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 12:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86f1abec458df24ea7d4a38a7b3e21861c5b9bd8 ***

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

Fix gdb/python/python.c use-after-free

Valgrind shows:

 ==26964== Invalid read of size 1
 ==26964==    at 0x6E14100: __GI_strcmp (strcmp.S:180)
 ==26964==    by 0x6DB55AA: setlocale (setlocale.c:238)
 ==26964==    by 0x4E0455: _initialize_python() (python.c:1731)
 ==26964==    by 0x786731: initialize_all_files() (init.c:319)
 ==26964==    by 0x72EF0A: gdb_init(char*) (top.c:1929)
 ==26964==    by 0x60BCAC: captured_main(void*) (main.c:863)
 ==26964==    by 0x606AD5: catch_errors(int (*)(void*), void*, char*, return_mask) (exceptions.c:234)
 ==26964==    by 0x60C608: gdb_main(captured_main_args*) (main.c:1165)
 ==26964==    by 0x40CAEC: main (gdb.c:32)
 ==26964==  Address 0x81d30a0 is 0 bytes inside a block of size 181 free'd
 ==26964==    at 0x4C29CF0: free (vg_replace_malloc.c:530)
 ==26964==    by 0x6DB5B65: setname (setlocale.c:201)
 ==26964==    by 0x6DB5B65: setlocale (setlocale.c:388)
 ==26964==    by 0x4E037F: _initialize_python() (python.c:1712)
 ==26964==    by 0x786731: initialize_all_files() (init.c:319)
 ==26964==    by 0x72EF0A: gdb_init(char*) (top.c:1929)
 ==26964==    by 0x60BCAC: captured_main(void*) (main.c:863)
 ==26964==    by 0x606AD5: catch_errors(int (*)(void*), void*, char*, return_mask) (exceptions.c:234)
 ==26964==    by 0x60C608: gdb_main(captured_main_args*) (main.c:1165)
 ==26964==    by 0x40CAEC: main (gdb.c:32)

The problem is doing this:

  oldloc = setlocale (LC_ALL, NULL);
  setlocale (LC_ALL, "");
  ...
  setlocale (LC_ALL, oldloc);

I.e., the second setlocale call frees 'oldloc'.

>From http://pubs.opengroup.org/onlinepubs/9699919799/functions/setlocale.html :

 "The returned string pointer might be invalidated or the string
 content might be overwritten by a subsequent call to setlocale()."

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

	PR python/20037
	* python/python.c (_initialize_python) [IS_PY3K]: xstrdup/xfree
	oldloc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM/STM32L4XX] PR 20030: --fix-stm32l4xx-629360 fails to create vldm/vpop veneers for double-precision registers
@ 2016-05-09 13:29 sergiodj+buildbot
  2016-05-09 19:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-09 13:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9239bbd3a6bf901dba1c0170622c50c78f6d1096 ***

Author: Christophe Monat <christophe.monat@st.com>
Branch: master
Commit: 9239bbd3a6bf901dba1c0170622c50c78f6d1096

[ARM/STM32L4XX] PR 20030: --fix-stm32l4xx-629360 fails to create vldm/vpop veneers for double-precision registers

bfd/
	PR ld/20030
	* elf32-arm.c (is_thumb2_vldm): Account for T1 (DP) encoding.
	(stm32l4xx_need_create_replacing_stub): Rename ambiguous nb_regs
	to nb_words.
	(create_instruction_vldmia): Add is_dp to disambiguate SP/DP
	encoding.
	(create_instruction_vldmdb): Likewise.
	(stm32l4xx_create_replacing_stub_vldm): is_dp detects DP encoding,
	uses it to re-encode.

ld/
	PR ld/20030
	* testsuite/ld-arm/arm-elf.exp: Run new stm32l4xx-fix-vldm-dp
	tests. Fix misnamed stm32l4xx-fix-all.
	* testsuite/ld-arm/stm32l4xx-fix-vldm-dp.s: New tests for multiple
	loads with DP registers.
	* testsuite/ld-arm/stm32l4xx-fix-vldm-dp.d: New reference file.
	* testsuite/ld-arm/stm32l4xx-fix-vldm.s: Add missing comment.
	* testsuite/ld-arm/stm32l4xx-fix-all.s: Add tests for multiple
	loads with DP registers.
	* testsuite/ld-arm/stm32l4xx-fix-all.d: Update reference.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't convert GOTPCREL relocation against large section
@ 2016-05-13 18:25 sergiodj+buildbot
  2016-05-13 20:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-13 18:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2168b2688ae343a61c467450068503295a5e3deb ***

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

Don't convert GOTPCREL relocation against large section

bfd/

	PR ld/20093
	* elf64-x86-64.c (elf_x86_64_convert_load_reloc): Don't convert
	GOTPCREL relocation against large section.

ld/

	PR ld/20093
	* testsuite/ld-x86-64/pr20093-1.d: New file.
	* testsuite/ld-x86-64/pr20093-1.s: Likewise.
	* testsuite/ld-x86-64/pr20093-2.d: Likewise.
	* testsuite/ld-x86-64/pr20093-2.s: Likewise.
	* testsuite/ld-x86-64/x86-64.exp: Run pr20093-1 and pr20093-2.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Reimplement .no87/.nommx/.nosse/.noavx directives
@ 2016-05-25 17:39 sergiodj+buildbot
  2016-05-26 20:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 293f5f65435c4d309cbf463e941a8bd5ae50c02d ***

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

Reimplement .no87/.nommx/.nosse/.noavx directives

Move all .noXXX directives to cpu_noarch.

gas/

	* config/tc-i386.c (arch_entry): Remove negated.
	(noarch_entry): New struct.
	(cpu_arch): Updated.  Remove .no87, .nommx, .nosse and .noavx.
	(cpu_noarch): New.
	(set_cpu_arch): Check cpu_noarch after cpu_arch.
	(md_parse_option): Allow -march=+nosse.  Check cpu_noarch after
	cpu_arch.
	(output_message): New function.
	(show_arch): Use it.  Handle cpu_noarch.
	* testsuite/gas/i386/i386.exp: Run nommx-1, nommx-2, nommx-3,
	nosse-1, nosse-2, nosse-3, noavx-1 and noavx-2.
	* testsuite/gas/i386/noavx-1.l: New file.
	* testsuite/gas/i386/noavx-1.s: Likewise.
	* testsuite/gas/i386/noavx-2.s: Likewise.
	* testsuite/gas/i386/noavx-2.l: Likewise.
	* testsuite/gas/i386/nommx-1.s: Likewise.
	* testsuite/gas/i386/nommx-1.l: Likewise.
	* testsuite/gas/i386/nommx-2.s: Likewise.
	* testsuite/gas/i386/nommx-2.l: Likewise.
	* testsuite/gas/i386/nommx-3.s: Likewise.
	* testsuite/gas/i386/nommx-3.l: Likewise.
	* testsuite/gas/i386/nosse-1.s: Likewise.
	* testsuite/gas/i386/nosse-1.l: Likewise.
	* testsuite/gas/i386/nosse-2.s: Likewise.
	* testsuite/gas/i386/nosse-2.l: Likewise.
	* testsuite/gas/i386/nosse-3.s: Likewise.
	* testsuite/gas/i386/nosse-3.l: Likewise.

opcodes/

	* i386-gen.c (cpu_flag_init): Rename CPU_ANY87_FLAGS to
	CPU_ANY_X87_FLAGS.  Add CPU_ANY_MMX_FLAGS.
	* i386-init.h: Regenerated.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] metag: add extern C to header
@ 2016-05-26 10:15 sergiodj+buildbot
  2016-05-27 10:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-26 10:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94740f9c4b20ec88a5e33823a4da13d6da311a22 ***

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

metag: add extern C to header

include/ChangeLog:

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

	* opcode/metag.h: wrap declarations in extern "C".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Don't stop processing on `bfd_reloc_outofrange'
@ 2016-05-26 11:56 sergiodj+buildbot
  2016-05-27 12:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-26 11:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed53407eec9eba3b55a3a00fb7eaa7eddbf01363 ***

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

MIPS/BFD: Don't stop processing on `bfd_reloc_outofrange'

Upon a `bfd_reloc_outofrange' error continue processing so that any
further issues are also reported, similarly to how `bfd_reloc_overflow'
is handled.  Adjust message formatting accordingly, using `%X' to abort
processing at conclusion.

Reduce the number of test cases by grouping relocations the handling of
which can now be verified together with a single source and dump.

	bfd/
	* elfxx-mips.c (_bfd_mips_elf_relocate_section)
	<bfd_reloc_outofrange>: Use the `%X%H' rather than `%C' format
	for message.  Continue processing rather than returning failure.

	ld/
	* testsuite/ld-mips-elf/unaligned-jalx-0.d: Fold
	`unaligned-jalx-2' here.
	* testsuite/ld-mips-elf/unaligned-jalx-mips16-0.d: Fold
	`unaligned-jalx-mips16-2' here.
	* testsuite/ld-mips-elf/unaligned-jalx-micromips-0.d: Fold
	`unaligned-jalx-micromips-2' here.
	* testsuite/ld-mips-elf/unaligned-jalx-0.s: Update accordingly.
	* testsuite/ld-mips-elf/unaligned-jalx-1.d: Update error
	message.
	* testsuite/ld-mips-elf/unaligned-jalx-mips16-1.d: Likewise.
	* testsuite/ld-mips-elf/unaligned-jalx-micromips-1.d: Likewise.
	* testsuite/ld-mips-elf/unaligned-jalx-2.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-jalx-mips16-2.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-jalx-micromips-2.d: Remove
	test.
	* testsuite/ld-mips-elf/unaligned-jalx-2.s: Remove test source.
	* testsuite/ld-mips-elf/unaligned-lwpc-0.d: Fold
	`unaligned-lwpc-3' here.
	* testsuite/ld-mips-elf/unaligned-lwpc-0.s: Update accordingly.
	* testsuite/ld-mips-elf/unaligned-lwpc-1.d: Fold
	`unaligned-lwpc-2' here.
	* testsuite/ld-mips-elf/unaligned-lwpc-1.s: Update accordingly.
	* testsuite/ld-mips-elf/unaligned-lwpc-2.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-lwpc-2.s: Remove test source.
	* testsuite/ld-mips-elf/unaligned-lwpc-3.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-lwpc-3.s: Remove test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-0.d: Fold
	`unaligned-ldpc-4' here.
	* testsuite/ld-mips-elf/unaligned-ldpc-0.s: Update accordingly.
	* testsuite/ld-mips-elf/unaligned-ldpc-1.d: Update error
	message.  Fold `unaligned-ldpc-2' and `unaligned-ldpc-3' here.
	* testsuite/ld-mips-elf/unaligned-ldpc-1.s: Update accordingly.
	* testsuite/ld-mips-elf/unaligned-ldpc-2.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-ldpc-2.s: Remove test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-3.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-ldpc-3.s: Remove test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-4.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-ldpc-4.s: Remove test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Delete removed tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT
@ 2016-05-27 12:58 sergiodj+buildbot
  2016-05-27 18:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 12:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51415b9f309443261016ad1b63b9e350bbe3903d ***

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

gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT

When evaluating an expression with EVAL_AVOID_SIDE_EFFECTS if the value
we return is forced to be of type not_lval then GDB will be unable to
take the address of the returned value.

Instead, we should properly initialise the LVAL of the returned value.

This commit builds on two previous commits 2520f728b710 (Forward
VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT) and
ac775bf4d35b (gdb: Forward VALUE_LVAL when avoiding side effects for
STRUCTOP_PTR), which in turn build on ac1ca910d74d (Fixes for PR
exp/15364).

This commit is currently untested due to my lack of access to an OpenCL
compiler, however, if follows the same pattern as the first two commits
mentioned above and so I believe that it is correct.

gdb/ChangeLog:

	* opencl-lang.c (evaluate_subexp_opencl): If
	EVAL_AVOID_SIDE_EFFECTS mode, forward the VALUE_LVAL attribute to
	the returned value in the STRUCTOP_STRUCT case.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix typo introduced during the most recent synchronization update.
@ 2016-05-27 13:49 sergiodj+buildbot
  2016-05-27 22:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 13:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1690f1db1ac7a4e91d81ae968b8158af2b7ff91f ***

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

Fix typo introduced during the most recent synchronization update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Correct CpuMax in i386-opc.h
@ 2016-05-27 14:08 sergiodj+buildbot
  2016-05-28  0:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 14:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e89c5eaa7208f06e927a79facff0316f4e550f6f ***

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

Correct CpuMax in i386-opc.h

CpuMax should be CpuIntel64, not CpuNo64.  i386-gen.c is updated to
verify that CpuMax is correct.  X86 assembler is updated to properly
set cpuamd64 and cpuintel64.

gas/

	PR gas/20154
	* config/tc-i386.c (intel64): New.
	(cpu_flags_match): Set cpuamd64 and cpuintel64.
	(md_parse_option): Set intel64 instead of cpuamd64 and
	cpuintel64.

opcodes/

	PR gas/20154
	* i386-gen.c (main): Fail if CpuMax is incorrect.
	* i386-opc.h (CpuMax): Set to CpuIntel64.
	* i386-tbl.h: Regenerated.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Replace CpuAMD64/CpuIntel64 with AMD64/Intel64
@ 2016-05-27 15:15 sergiodj+buildbot
  2016-05-28  2:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 15:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e92bae62606702c1c07e095789ffed103e0e34c5 ***

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

Replace CpuAMD64/CpuIntel64 with AMD64/Intel64

AMD64 vs CpuIntel64 ISA should be handled similar as AT&T vs Intel
syntax.  Since cpu_flags isn't sorted by position, we need to check
the whole cpu_flags array for the maximum position when verifying
CpuMax.

gas/

	PR gas/20154
	* config/tc-i386.c (cpu_flags_match): Don't set cpuamd64 nor
	cpuintel64.
	(match_template): Check Intel64/AMD64 ISA.

opcodes/

	PR gas/20154
	* i386-gen.c (cpu_flags): Remove CpuAMD64 and CpuIntel64.
	(opcode_modifiers): Add AMD64 and Intel64.
	(main): Properly verify CpuMax.
	* i386-opc.h (CpuAMD64): Removed.
	(CpuIntel64): Likewise.
	(CpuMax): Set to CpuNo64.
	(i386_cpu_flags): Remove cpuamd64 and cpuintel64.
	(AMD64): New.
	(Intel64): Likewise.
	(i386_opcode_modifier): Add amd64 and intel64.
	(i386-opc.tbl): Replace CpuAMD64/CpuIntel64 with AMD64/Intel64
	on call and jmp.
	* i386-init.h: Regenerated.
	* i386-tbl.h: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Skip attach-many-short-lived-threads.exp on known-broken DejaGnu versions
@ 2016-05-27 15:32 sergiodj+buildbot
  2016-05-28  2:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 15:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 744608cc854a365661e93d307aadf22ab6e6bd7c ***

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

Skip attach-many-short-lived-threads.exp on known-broken DejaGnu versions

If the testsuite is run with a DejaGnu version that predates the fix
from last year:

  [PATCH] DejaGnu kills the wrong process due to PID-reuse races
  http://lists.gnu.org/archive/html/dejagnu/2015-07/msg00005.html

... gdb.threads/attach-many-short-lived-threads.exp fails randomly,
often.  Other tests randomly fail due to that issue too, but this one
is _much_ more exposed.

DejaGnu 1.6 was released meanwhile, which includes that DejaGnu fix,
and also some distros backported the fix too.

So skip the test when run with older/broken DejaGnus.

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

	* gdb.threads/attach-many-short-lived-threads.exp (bad_dejagnu):
	New procedure.
	(top level): Call it, and bail out of DejaGnu is known to be bad.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Update x86 CPU_XXX_FLAGS handling
@ 2016-05-27 17:19 sergiodj+buildbot
  2016-05-28  4:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 17:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1848e567343e9c50979453463f34e0a55ba892eb ***

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

Update x86 CPU_XXX_FLAGS handling

Support defining CPU_XXX_FLAGS with other CPU_XXX_FLAGS.  Update
CPU_XXX_FLAGS to enable more bits like x87 and SYSCALL.  Don't enable
MMX when enabling SSE, AVX or AVX512.  Don't disable AVX nor AVX512 when
disabling SSE.  Don't disable AVX512 when disabling AVX.  Disable F16C,
FMA, FMA4 and XOP when disabling AVX.  Add 87, no287, no387, no687,
nosse2, nosse3, nossse3, nosse4.1, nosse4.2, nosse4 and noavx2 directives
to x86 assembler.

TODO: Add more .noXXX, like .noavx512f, directives to x86 assembler.

gas/

	PR gas/20145
	* config/tc-i386.c (cpu_arch): Add 687.
	(cpu_noarch): Add no287, no387, no687, nosse2, nosse3, nossse3,
	nosse4.1, nosse4.2, nosse4 and noavx2.
	(parse_real_register): Check cpuregmmx instead of cpummx for MMX
	register.  Check cpuregxmm instead of cpusse for XMM register.
	Check cpuregymm instead of cpuavx for YMM register.  Check
	cpuregzmm/cpuregmask instead of cpuavx512f for ZMMM/mask register.
	* doc/c-i386.texi: Mention 687, no287, no387, no687, nosse2,
	nosse3, nossse3, nosse4.1, nosse4.2, nosse4 and noavx2.
	* testsuite/gas/i386/arch-10-prefetchw.d (as): Add mmx.
	* testsuite/gas/i386/arch-10.d (as): Likewise.
	* testsuite/gas/i386/arch-11.s: Add ".arch .mmx".
	* testsuite/gas/i386/i386.exp: Pass mmx to assembler for
	arch-10-3 and arch-10-4.  Run no87-3, nosse-4, nosse-5, noavx-3
	and noavx-4.
	* testsuite/gas/i386/no87-3.l: New file.
	* testsuite/gas/i386/no87-3.s: Likewise.
	* testsuite/gas/i386/noavx-3.l: Likewise.
	* testsuite/gas/i386/noavx-3.s: Likewise.
	* testsuite/gas/i386/noavx-4.d: Likewise.
	* testsuite/gas/i386/noavx-4.s: Likewise.
	* testsuite/gas/i386/nosse-4.l: Likewise.
	* testsuite/gas/i386/nosse-4.s: Likewise.
	* testsuite/gas/i386/nosse-5.d: Likewise.
	* testsuite/gas/i386/nosse-5.s: Likewise.

opcodes/

	PR gas/20145
	* i386-gen.c (cpu_flag_init): Update CPU_XXX_FLAGS.  Remove
	CpuMMX from CPU_SSE_FLAGS.  Remove AVX and AVX512 bits from
	CPU_ANY_SSE_FLAGS.  Remove AVX512 bits from CPU_ANY_AVX_FLAGS.
	Add CPU_XSAVE_FLAGS to CPU_XSAVEOPT_FLAGS, CPU_XSAVE_FLAGS and
	CpuXSAVEC.  Add CPU_AVX_FLAGS to CpuF16C.  Remove CpuMMX from
	CPU_AVX512F_FLAGS, CPU_AVX512CD_FLAGS, CPU_AVX512ER_FLAGS,
	CPU_AVX512PF_FLAGS, CPU_AVX512DQ_FLAGS and CPU_AVX512BW_FLAGS.
	Add CPU_SSE2_FLAGS to CPU_SHA_FLAGS.   Add CPU_ANY_287_FLAGS,
	CPU_ANY_387_FLAGS, CPU_ANY_687_FLAGS, CPU_ANY_SSE2_FLAGS,
	CPU_ANY_SSE3_FLAGS, CPU_ANY_SSSE3_FLAGS, CPU_ANY_SSE4_1_FLAGS,
	CPU_ANY_SSE4_2_FLAGS and CPU_ANY_AVX2_FLAGS.  Enable CpuRegMMX
	for MMX.  Enable CpuRegXMM for SSE, AVX and AVX512.  Enable
	CpuRegYMM for AVX and AVX512VL,  Enable CpuRegZMM and
	CpuRegMask for AVX512.
	(cpu_flags): Add CpuRegMMX, CpuRegXMM, CpuRegYMM, CpuRegZMM
	and CpuRegMask.
	(set_bitfield_from_cpu_flag_init): New function.
	(set_bitfield): Remove const on f.  Call
	set_bitfield_from_cpu_flag_init to handle CPU_XXX_FLAGS.
	* i386-opc.h (CpuRegMMX): New.
	(CpuRegXMM): Likewise.
	(CpuRegYMM): Likewise.
	(CpuRegZMM): Likewise.
	(CpuRegMask): Likewise.
	(i386_cpu_flags): Add cpuregmmx, cpuregxmm, cpuregymm, cpuregzmm
	and cpuregmask.
	* i386-init.h: Regenerated.
	* i386-tbl.h: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Fix section symbol name fetching in relocation
@ 2016-05-27 21:56 sergiodj+buildbot
  2016-05-28  6:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 21:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ceab86af75e9870ecf2da772a0d867ca12521a24 ***

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

MIPS/BFD: Fix section symbol name fetching in relocation

Symbol table entries for section symbols are different between IRIX and
traditional MIPS ELF targets in that IRIX entries have their `st_name'
member pointing at the section's name in the string table section, while
traditional entries have 0 there and the section header string table has
to be referred via the relevant section header's `shn_name' member
instead.

This is chosen with the `elf_backend_name_local_section_symbols' backend
and can be observed with `readelf -s' output for an IRIX object:

Symbol table '.symtab' contains 12 entries:
   Num:    Value  Size Type    Bind   Vis      Ndx Name
     0: 00000000     0 NOTYPE  LOCAL  DEFAULT  UND
     1: 00000000     0 SECTION LOCAL  DEFAULT    1 .text
     2: 00000000     0 SECTION LOCAL  DEFAULT    3 .data
     3: 00000000     0 SECTION LOCAL  DEFAULT    4 .bss
     4: 00000000     0 SECTION LOCAL  DEFAULT    5 .reginfo
     5: 00000000     0 SECTION LOCAL  DEFAULT    6 .MIPS.abiflags
     6: 00000000     0 SECTION LOCAL  DEFAULT    7 .pdr
     7: 00000000     0 SECTION LOCAL  DEFAULT    9 .gnu.attributes
     8: 00002000    16 FUNC    GLOBAL DEFAULT    1 foo
     9: 00004008     0 FUNC    LOCAL  DEFAULT    1 abar
    10: 00002008     0 FUNC    LOCAL  DEFAULT    1 afoo
    11: 00004000    16 FUNC    GLOBAL DEFAULT    1 bar

and a corresponding traditional object:

Symbol table '.symtab' contains 12 entries:
   Num:    Value  Size Type    Bind   Vis      Ndx Name
     0: 00000000     0 NOTYPE  LOCAL  DEFAULT  UND
     1: 00000000     0 SECTION LOCAL  DEFAULT    1
     2: 00000000     0 SECTION LOCAL  DEFAULT    3
     3: 00000000     0 SECTION LOCAL  DEFAULT    4
     4: 00004008     0 FUNC    LOCAL  DEFAULT    1 abar
     5: 00002008     0 FUNC    LOCAL  DEFAULT    1 afoo
     6: 00000000     0 SECTION LOCAL  DEFAULT    5
     7: 00000000     0 SECTION LOCAL  DEFAULT    6
     8: 00000000     0 SECTION LOCAL  DEFAULT    7
     9: 00000000     0 SECTION LOCAL  DEFAULT    9
    10: 00002000    16 FUNC    GLOBAL DEFAULT    1 foo
    11: 00004000    16 FUNC    GLOBAL DEFAULT    1 bar

respectively.  Consequently the right way to retrieve a section symbol's
name has to be chosen in `mips_elf_calculate_relocation' for the purpose
of error reporting.

Originally we produced symbol tables in the traditional object format
only and we handled it correctly until it was lost in a rewrite with:

commit 7403cb6305f5660fccc8869d3333a731102ae978
Author: Mark Mitchell <mark@codesourcery.com>
Date:   Wed Jun 30 20:13:43 1999 +0000

probably because of the extra pointer indirection added which made the
same expression have a different meaning.

With the addition of IRIX symbol table format with:

commit 174fd7f9556183397625dbfa99ef68ecd325c74b
Author: Richard Sandiford <rdsandiford@googlemail.com>
Date:   Mon Feb 9 08:04:00 2004 +0000

the bug has been partially covered and now when a relocation error is
triggered with an IRIX object the offending section symbol is correctly
reported:

tmpdir/dump0.o: In function `foo':
(.text+0x2000): relocation truncated to fit: R_MIPS_26 against `.text'
tmpdir/dump0.o: In function `bar':
(.text+0x4000): relocation truncated to fit: R_MIPS_26 against `.text'

because `bfd_elf_string_from_elf_section' retrieves the name from the
string table section.  With a traditional object however the function
returns an empty string and consequently `no symbol' is printed instead:

tmpdir/dump0.o: In function `foo':
(.text+0x2000): relocation truncated to fit: R_MIPS_26 against `no symbol'
tmpdir/dump0.o: In function `bar':
(.text+0x4000): relocation truncated to fit: R_MIPS_26 against `no symbol'

Restore the original semantics so that the section name is always
correctly retrieved.

	bfd/
	* elfxx-mips.c (mips_elf_calculate_relocation): Also use the
	section name if `bfd_elf_string_from_elf_section' returns an
	empty string.

	ld/
	* testsuite/ld-mips-elf/reloc-local-overflow.d: New test.
	* testsuite/ld-mips-elf/reloc-local-overflow.s: Source for the
	new test.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Include the addend in JALX's target alignment verification
@ 2016-05-27 22:07 sergiodj+buildbot
  2016-05-28  7:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 22:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc27bb0573a5e1ce1a6365fc06aeab9bd891fc3a ***

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

MIPS/BFD: Include the addend in JALX's target alignment verification

On RELA targets the addend can affect JALX target's alignment, so only
verify it once the whole relocation calculation has completed.

	bfd/
	* elfxx-mips.c (mips_elf_calculate_relocation) <R_MIPS16_26>
	<R_MIPS_26, R_MICROMIPS_26_S1>: Include the addend in JALX's
	target alignment verification.

	ld/
	* testsuite/ld-mips-elf/unaligned-jalx-addend-0.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-1.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-mips16-0.d: New
	test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-mips16-1.d: New
	test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-micromips-0.d: New
	test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-micromips-1.d: New
	test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-0.s: New test
	source.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-1.s: New test
	source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Return void from linker callbacks
@ 2016-05-28  2:08 sergiodj+buildbot
  2016-05-28  8:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-28  2:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a72702bb30ec3f94627cfcae684823b413f20b9 ***

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

Return void from linker callbacks

The ldmain.c implementation of these linker callback functions always
return true, so any code handling a false return is dead.  What's
more, some of the bfd backends abort if ever a false return is seen,
and there seems to be some confusion in gdb's compile-object-load.c.
The return value was never meant to be "oh yes, a multiple_definition
error occurred", but rather "out of memory or other catastrophic
failure".

This patch removes the status return on the callbacks that always
return true.  I kept the return status for "notice" because that one
does happen to need to return "out of memory".

include/
	* bfdlink.h (struct bfd_link_callbacks): Update comments.
	Return void from multiple_definition, multiple_common,
	add_to_set, constructor, warning, undefined_symbol,
	reloc_overflow, reloc_dangerous and unattached_reloc.
bfd/
	* aoutx.h: Adjust linker callback calls throughout file,
	removing dead code.
	* bout.c: Likewise.
	* coff-alpha.c: Likewise.
	* coff-arm.c: Likewise.
	* coff-h8300.c: Likewise.
	* coff-h8500.c: Likewise.
	* coff-i960.c: Likewise.
	* coff-mcore.c: Likewise.
	* coff-mips.c: Likewise.
	* coff-ppc.c: Likewise.
	* coff-rs6000.c: Likewise.
	* coff-sh.c: Likewise.
	* coff-tic80.c: Likewise.
	* coff-w65.c: Likewise.
	* coff-z80.c: Likewise.
	* coff-z8k.c: Likewise.
	* coff64-rs6000.c: Likewise.
	* cofflink.c: Likewise.
	* ecoff.c: Likewise.
	* elf-bfd.h: Likewise.
	* elf-m10200.c: Likewise.
	* elf-m10300.c: Likewise.
	* elf32-arc.c: Likewise.
	* elf32-arm.c: Likewise.
	* elf32-avr.c: Likewise.
	* elf32-bfin.c: Likewise.
	* elf32-cr16.c: Likewise.
	* elf32-cr16c.c: Likewise.
	* elf32-cris.c: Likewise.
	* elf32-crx.c: Likewise.
	* elf32-d10v.c: Likewise.
	* elf32-epiphany.c: Likewise.
	* elf32-fr30.c: Likewise.
	* elf32-frv.c: Likewise.
	* elf32-ft32.c: Likewise.
	* elf32-h8300.c: Likewise.
	* elf32-hppa.c: Likewise.
	* elf32-i370.c: Likewise.
	* elf32-i386.c: Likewise.
	* elf32-i860.c: Likewise.
	* elf32-ip2k.c: Likewise.
	* elf32-iq2000.c: Likewise.
	* elf32-lm32.c: Likewise.
	* elf32-m32c.c: Likewise.
	* elf32-m32r.c: Likewise.
	* elf32-m68hc1x.c: Likewise.
	* elf32-m68k.c: Likewise.
	* elf32-mep.c: Likewise.
	* elf32-metag.c: Likewise.
	* elf32-microblaze.c: Likewise.
	* elf32-moxie.c: Likewise.
	* elf32-msp430.c: Likewise.
	* elf32-mt.c: Likewise.
	* elf32-nds32.c: Likewise.
	* elf32-nios2.c: Likewise.
	* elf32-or1k.c: Likewise.
	* elf32-ppc.c: Likewise.
	* elf32-s390.c: Likewise.
	* elf32-score.c: Likewise.
	* elf32-score7.c: Likewise.
	* elf32-sh.c: Likewise.
	* elf32-sh64.c: Likewise.
	* elf32-spu.c: Likewise.
	* elf32-tic6x.c: Likewise.
	* elf32-tilepro.c: Likewise.
	* elf32-v850.c: Likewise.
	* elf32-vax.c: Likewise.
	* elf32-visium.c: Likewise.
	* elf32-xstormy16.c: Likewise.
	* elf32-xtensa.c: Likewise.
	* elf64-alpha.c: Likewise.
	* elf64-hppa.c: Likewise.
	* elf64-ia64-vms.c: Likewise.
	* elf64-mmix.c: Likewise.
	* elf64-ppc.c: Likewise.
	* elf64-s390.c: Likewise.
	* elf64-sh64.c: Likewise.
	* elf64-x86-64.c: Likewise.
	* elflink.c: Likewise.
	* elfnn-aarch64.c: Likewise.
	* elfnn-ia64.c: Likewise.
	* elfxx-mips.c: Likewise.
	* elfxx-sparc.c: Likewise.
	* elfxx-tilegx.c: Likewise.
	* linker.c: Likewise.
	* pdp11.c: Likewise.
	* pe-mips.c: Likewise.
	* reloc.c: Likewise.
	* reloc16.c: Likewise.
	* simple.c: Likewise.
	* vms-alpha.c: Likewise.
	* xcofflink.c: Likewise.
	* elf32-rl78.c (get_symbol_value, get_romstart, get_ramstart): Delete
	status param.  Adjust calls to these and linker callbacks throughout.
	* elf32-rx.c: (get_symbol_value, get_gp, get_romstart,
	get_ramstart): Delete status param.  Adjust calls to these and
	linker callbacks throughout.
ld/
	* ldmain.c (multiple_definition, multiple_common, add_to_set,
	constructor_callback, warning_callback, undefined_symbol,
	reloc_overflow, reloc_dangerous, unattached_reloc): Return void.
	* emultempl/elf32.em: Adjust callback calls.
gdb/
	* compile/compile-object-load.c (link_callbacks_multiple_definition,
	link_callbacks_warning, link_callbacks_undefined_symbol,
	link_callbacks_undefined_symbol, link_callbacks_reloc_overflow,
	link_callbacks_reloc_dangerous,
	link_callbacks_unattached_reloc): Return void.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Enable local R_MIPS_26 overflow detection
@ 2016-05-28 10:13 sergiodj+buildbot
  2016-05-28 11:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-28 10:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7743482350c9c97484a429070db7d994a643a9eb ***

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

MIPS/BFD: Enable local R_MIPS_26 overflow detection

The original MIPS SVR4 psABI defines the calculation for the R_MIPS_26
relocation in a complex way, as follows[1]:

Name        Value Field    Symbol   Calculation
R_MIPS_26     4   T-targ26 local    (((A << 2) | \
                                      (P & 0xf0000000)) + S) >> 2
              4   T-targ26 external (sign-extend(A << 2) + S) >> 2

This is further clarified, by correcting typos (already applied in the
excerpt above) in the 64-bit psABI extension[2].  A note is included in
both documents to specify that for the purpose of relocation processing
a local symbol is one with binding STB_LOCAL and type STT_SECTION, and
otherwise, a symbol is external.

We have both calculations implemented for the R_MIPS_26 relocation, and
by extension also for the R_MIPS16_26 and R_MICROMIPS_26_S1 relocations,
from now on collectively called jump relocations.  However our code uses
a different condition to tell local and external symbols apart, that is
it only checks for the STB_LOCAL binding and ignores the symbol type,
however for REL relocations only.  The external calculation is used for
all RELA jump relocations.

In reality the difference matters for jump relocations referring local
MIPS16 and, as from recent commit 44d3da233815 ("MIPS/GAS: Treat local
jump relocs the same no matter if REL or RELA"), also local microMIPS
symbols.  Such relocations are not converted to refer to corresponding
section symbols instead and retain the original local symbol reference.

It can be inferred from the relocation calculation definitions that the
addend is effectively unsigned for the local case and explicitly signed
for the external case.  With the REL relocation format it makes sense
given the limited range provided for by the field being relocated: the
use of an unsigned addend expands the range by one bit for the local
case, because a negative offset from a section symbol makes no sense,
and any usable negative offset from the original local symbol will have
worked out positive if converted to a section-relative reference.  In
the external case a signed addend gives more flexibility as offsets both
negative and positive can be used with a symbol.  Any such offsets will
typically have a small value.

The inclusion of the (P & 0xf0000000) component, ORed in the calculation
in the local case, seems questionable as bits 31:28 are not included in
the relocatable field and are masked out as the relocation is applied.
Their value is therefore irrelevant for output processing, the relocated
field ends up the same regardless of their value.  They could be used
for overflow detection, however this is precluded by adding them to bits
31:28 of the symbol referred, as the sum will not correspond to the
value calculated by the processor at run time whenever bits 31:28 of the
symbol referred are not all zeros, even though it is valid as long they
are the same as bits 31:28 of P.

We deal with this problem by ignoring any overflow resulting from the
local calculation.  This however makes us miss genuine overflow cases,
where 31:28 of the symbol referred are different from bits 31:28 of P,
and non-functional code is produced.

Given the situation, for the purpose of overflow detection we can change
our code to follow the original psABI and only treat the in-place addend
as unsigned in the section symbol case, permitting jumps to offsets
128MiB and above into section.  Sections so large may be uncommon, but
still a reasonable use case.  On the other hand such large offsets from
regular local symbols are not expected and it makes sense to support
(possibly small) negative offsets instead, also in consistency with what
we do for global symbols.

Drop the (P & 0xf0000000) component then, treat the addend as signed
with local non-section symbols and also detect an overflow in the result
of such calculation with local symbols.  NB it does not affect the value
computed for the relocatable field, it only affects overflow detection.

References:

[1] "SYSTEM V APPLICATION BINARY INTERFACE, MIPS RISC Processor
    Supplement, 3rd Edition", Figure 4-11: "Relocation Types", p. 4-19
    <http://www.linux-mips.org/pub/linux/mips/doc/ABI/mipsabi.pdf>

[2] "64-bit ELF Object File Specification, Draft Version 2.5", Table 32
    "Relocation Types", p. 45
    <http://techpubs.sgi.com/library/manuals/4000/007-4658-001/pdf/007-4658-001.pdf>

	bfd/
	* elfxx-mips.c (mips_elf_calculate_relocation): <R_MIPS16_26>
	<R_MIPS_26, R_MICROMIPS_26_S1>: Drop the region bits of the
	reloc location from calculation, treat the addend as signed with
	local non-section symbols and enable overflow detection.

	ld/
	* testsuite/ld-mips-elf/jal-global-overflow-0.d: New test.
	* testsuite/ld-mips-elf/jal-global-overflow-1.d: New test.
	* testsuite/ld-mips-elf/jal-local-overflow-0.d: New test.
	* testsuite/ld-mips-elf/jal-local-overflow-1.d: New test.
	* testsuite/ld-mips-elf/jal-global-overflow.s: New test source.
	* testsuite/ld-mips-elf/jal-local-overflow.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Correctly handle `bfd_reloc_outofrange' with branches
@ 2016-05-28 10:23 sergiodj+buildbot
  2016-05-28 12:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-28 10:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99aefae6818be07a77739e0366121f2032916d9c ***

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

MIPS/BFD: Correctly handle `bfd_reloc_outofrange' with branches

Fix internal errors like:

ld: BFD (GNU Binutils) 2.26.51.20160526 internal error, aborting at .../bfd/elfxx-mips.c:10278 in _bfd_mips_elf_relocate_section

ld: Please report this bug.

triggered by the `bfd_reloc_outofrange' condition on branch relocations.

	bfd/
	* elfxx-mips.c (b_reloc_p): New function.
	(_bfd_mips_elf_relocate_section) <bfd_reloc_outofrange>: Handle
	branch relocations.

	ld/
	* testsuite/ld-mips-elf/unaligned-branch.d: New test.
	* testsuite/ld-mips-elf/unaligned-branch.s: New test source.
	* testsuite/ld-mips-elf/unaligned-text.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add dependencies to configure rule
@ 2016-05-28 13:19 sergiodj+buildbot
  2016-05-28 14:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-28 13:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0597bdc443005c70f0fd474279098ee17db882eb ***

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

Add dependencies to configure rule

	* Makefile.tpl (configure): Depend on m4 files included.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add .noavx512XX directives to x86 assembler
@ 2016-05-29 15:10 sergiodj+buildbot
  2016-05-29 16:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-29 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 144b71e2a88e02d0b54d4f09cc652f353b46e455 ***

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

Add .noavx512XX directives to x86 assembler

Add .noavx512f, .noavx512cd, .noavx512er, .noavx512pf, .noavx512dq,
.noavx512bw, .noavx512vl, .noavx512ifma, .noavx512vbmi directives to x86
assembler.

gas/

	PR gas/20145
	* config/tc-i386.c (cpu_noarch): Add noavx512f, noavx512cd,
	noavx512er, noavx512pf, noavx512dq, noavx512bw, noavx512vl,
	noavx512ifma and noavx512vbmi.
	* doc/c-i386.texi: Mention noavx512f, noavx512cd, noavx512er,
	noavx512pf, noavx512dq, noavx512bw, noavx512vl, noavx512ifma
	and noavx512vbmi.
	* testsuite/gas/i386/i386.exp: Run noavx512-1 and noavx512-2.
	* testsuite/gas/i386/noavx512-1.l: New file.
	* testsuite/gas/i386/noavx512-1.s: Likewise.
	* testsuite/gas/i386/noavx512-2.l: Likewise.
	* testsuite/gas/i386/noavx512-2.s: Likewise.

opcodes/

	PR gas/20145
	* i386-gen.c (cpu_flag_init): Add CPU_ANY_AVX512F_FLAGS,
	CPU_ANY_AVX512CD_FLAGS, CPU_ANY_AVX512ER_FLAGS,
	CPU_ANY_AVX512PF_FLAGS, CPU_ANY_AVX512DQ_FLAGS,
	CPU_ANY_AVX512BW_FLAGS, CPU_ANY_AVX512VL_FLAGS,
	CPU_ANY_AVX512IFMA_FLAGS and CPU_ANY_AVX512VBMI_FLAGS.
	* i386-init.h: Regenerated.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] NEWS: Remove empty line.
@ 2016-05-29 16:52 sergiodj+buildbot
  2016-05-29 17:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-29 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c64e0f6165537efda112a9744e588f4ecac8ca41 ***

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

NEWS: Remove empty line.

gdb/ChangeLog
2016-05-29  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* NEWS (N stop reply): Remove empty line.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] NEWS: QCatchSyscalls: simplify
@ 2016-05-29 18:59 sergiodj+buildbot
  2016-05-29 19:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-29 18:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aab3c527d779a8e833a469203336afcc17512559 ***

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

NEWS: QCatchSyscalls: simplify

Standardize the QCatchSyscalls NEWS entry.

gdb/ChangeLog
2016-05-29  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* NEWS (QCatchSyscalls): Remove the parameter.  Include ...
	(QCatchSyscalls:1 in qSupported) ... this separate entry which got
	deleted.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum
@ 2016-05-30 12:29 sergiodj+buildbot
  2016-05-30 13:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 12:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a2b436ae9958a1029545c03201b7223ff33c150 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 3a2b436ae9958a1029545c03201b7223ff33c150

Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum

Make the code (maybe) more readable + primarily prepare it for [patch 2/2]
enum extension.

This change should have no code change impact.

gdb/ChangeLog
2016-05-30  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum
	* dwarf2read.c (enum pc_bounds_kind) New.
	(dwarf2_get_pc_bounds): Use it in the declaration.
	(process_psymtab_comp_unit_reader): Adjust caller.  Rename has_pc_info
	to cu_bounds_kind.
	(read_func_scope, read_lexical_block_scope, read_call_site_scope):
	Adjust callers.
	(dwarf2_get_pc_bounds): Use enum pc_bounds_kind in the definition.
	(dwarf2_get_subprogram_pc_bounds, get_scope_pc_bounds): Adjust callers.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR 15231: import bare DW_TAG_lexical_block
@ 2016-05-30 12:38 sergiodj+buildbot
  2016-05-30 14:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 12:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e385593eef98ac92be57159e141f4b805dadbbb3 ***

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

PR 15231: import bare DW_TAG_lexical_block

Local variables in lambdas are not accessible
https://sourceware.org/bugzilla/show_bug.cgi?id=15231

GDB: read_lexical_block_scope
  /* Ignore blocks with missing or invalid low and high pc attributes.  */
[...]
  if (!dwarf2_get_pc_bounds (die, &lowpc, &highpc, cu, NULL))
    return;

But sometimes there is:

FAIL: gcc-5.3.1-6.fc23.x86_64
 <2><92>: Abbrev Number: 11 (DW_TAG_lexical_block)
 <3><9c>: Abbrev Number: 13 (DW_TAG_structure_type)
    <9d>   DW_AT_name        : (indirect string, offset: 0x3c): <lambda()>
    [...]

Where DW_TAG_lexical_block has no attributes.  Such whole subtree is currently
dropped by GDB while I think it should just import all its children DIEs.

It even XFAIL->XPASSes gdb.ada/out_of_line_in_inlined.exp:
	commit 0fa7fe506c242b459c4c05d331e7c7d66fb52390
	Author: Joel Brobecker <brobecker@adacore.com>
	    out of line functions nested inside inline functions.
So I have removed that xfail.

gdb/ChangeLog
2016-05-30  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR c++/15231
	* dwarf2read.c (enum pc_bounds_kind): Add PC_BOUNDS_INVALID.
	(process_psymtab_comp_unit_reader, read_func_scope): Adjust callers.
	(read_lexical_block_scope): Import DIEs from bare DW_TAG_lexical_block.
	(read_call_site_scope): Adjust callers.
	(dwarf2_get_pc_bounds): Implement pc_bounds_invalid.
	(dwarf2_get_subprogram_pc_bounds, get_scope_pc_bounds): Adjust callers.

gdb/testsuite/ChangeLog
2016-05-30  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR c++/15231
	* gdb.ada/out_of_line_in_inlined.exp: Remove xfails.
	* gdb.dwarf2/dw2-lexical-block-bare.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add counter-cases for trace-condition.exp tests
@ 2016-05-30 17:04 sergiodj+buildbot
  2016-05-30 17:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7faeb45ae36426b827c49457cf7186d73756cccc ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 7faeb45ae36426b827c49457cf7186d73756cccc

Add counter-cases for trace-condition.exp tests

In trace-condition.exp, tests are done by doing a conditional tracepoint
and validating that the trace contains all the frames that could be
collected if that condition is true.

E.g. test_tracepoints $trace_command "21 + 21 == 42" 10

This will always return true and collect the 10 frames possible to collect
with the test program.

However, if the condition evaluation is broken such that the condition is
unconditional we will not notice this problem.

This patch adds counter-cases to such conditions like so:

$trace_command "21 + 11 == 42" 0

This way such a problem would be noticed.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-condition.exp: Add counter-case tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Move trace conditions tests from ftrace.exp to trace-condition.exp
@ 2016-05-30 17:13 sergiodj+buildbot
  2016-05-30 18:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0d33646690c2e88624cd9646539d63d4144d03e8 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 0d33646690c2e88624cd9646539d63d4144d03e8

Move trace conditions tests from ftrace.exp to trace-condition.exp

This patch moves conditional tests that were done in ftrace.exp to
trace-condition.exp.

Note that emit_ref is now tested by the anarg local variable there is no
need to test the register directly.

All emit calls have been tested using asserts before / after the move, to
ensure that the tests cover the same functions.

Note that these function were not covered before and are still not:
emit_gt_goto, emit_lt_goto, emit_pop, emit_unsigned_less.

gdb/testsuite/ChangeLog:

	* gdb.trace/ftrace.exp (test_ftrace_condition): Remove.
	Move condition tests...
	* gdb.trace/trace-condition.exp: Here.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add emit_less_unsigned test in trace-condition.exp
@ 2016-05-30 17:22 sergiodj+buildbot
  2016-05-30 19:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a781823347ec9cd84e5ccc0bb8ddde48f8d302b6 ***

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

Add emit_less_unsigned test in trace-condition.exp

This patch adds coverage for emit_less_unsigned.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-condition.exp: Add emit_less_unsigned test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add variable length tests for emit_ref in trace-condition.exp
@ 2016-05-30 17:30 sergiodj+buildbot
  2016-05-30 21:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2320162a6219c664a8da2e2ff68b08d6f6c2ffcc ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 2320162a6219c664a8da2e2ff68b08d6f6c2ffcc

Add variable length tests for emit_ref in trace-condition.exp

This patch add variable length tests for emit_ref by reading the variable
passed as argument of 8 to 64 bit.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-condition.c (marker): Adapt signature to 8 to 64
	bits types.
	(main): Adapt to 8 to 64 bits types.
	* gdb.trace/trace-condition.exp: Add new tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add tests for 64bit values in trace-condition.exp
@ 2016-05-30 17:39 sergiodj+buildbot
  2016-05-30 21:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 825c8ef28fc669bdf4eab64b43d7a64761fbd677 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 825c8ef28fc669bdf4eab64b43d7a64761fbd677

Add tests for 64bit values in trace-condition.exp

This patch adds tests for emit operations with 64 bit values. It takes
special care to avoid mistakes that one could make on a 32bit architecture
using 64bit values.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-condition.exp: Add 64bit tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't needlessly clear xmemdup allocated memory.
@ 2016-05-31 11:20 sergiodj+buildbot
  2016-05-31 12:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-31 11:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c12969f8b53659f0d70b5e049c49b97a96826a3f ***

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

Don't needlessly clear xmemdup allocated memory.

	* xmemdup.c (xmemdup): Use xmalloc rather than xcalloc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [PR gdb/19893] Fix handling of synthetic C++ references
@ 2016-05-31 19:07 sergiodj+buildbot
  2016-05-31 20:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-05-31 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3326303bf5ae4c92f2fbbff387ce231a16c1c8bf ***

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

[PR gdb/19893] Fix handling of synthetic C++ references

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

I've traced the main source of the problem to pieced_value_funcs.coerce_ref not being
implemented. Since gdb always assumes references are implemented as pointers, this
causes it to think that it's dealing with a NULL pointer, thus breaking any operations
involving synthetic references.

What I did here was implementing pieced_value_funcs.coerce_ref using some of the synthetic
pointer handling code from indirect_pieced_value, as Pedro suggested. I also made a few
adjustments to the reference printing code so that it correctly shows either the address
of the referenced value or (if it's non-addressable) the "<synthetic pointer>" string.

I also wrote some unit tests based on Dwarf::assemble; these took a while to make
because in most cases I needed a synthetic reference to a physical variable. Additionally,
I started working on a unit test for classes that have a vtable, but ran into a few issues
so that'll probably go in a future patch. One thing that should definitely be fixed is that
proc function_range (called for MACRO_AT_func) will always try to compile/link using gcc
with the default options instead of g++, thus breaking C++ compilations that require e.g. libstdc++.

gdb/ChangeLog:

	* dwarf2loc.c (coerce_pieced_ref, indirect_synthetic_pointer,
	fetch_const_value_from_synthetic_pointer): New functions.
	(indirect_pieced_value): Move lower half to indirect_synthetic_pointer.
	(pieced_value_funcs): Implement coerce_ref.
	* valops.c (value_addr): Call coerce_ref for synthetic references.
	* valprint.c (valprint_check_validity): Return true for synthetic
	references.  Also, don't show "<synthetic pointer>" if they reference
	addressable values.
	(generic_val_print_ref): Handle synthetic references.  Also move some
	code to print_ref_address.
	(print_ref_address, get_value_addr_contents): New functions.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/implref.exp: Rename to...
	* gdb.dwarf2/implref-const.exp: ...this.  Also add more test statements.
	* gdb.dwarf2/implref-array.c: New file.
	* gdb.dwarf2/implref-array.exp: Likewise.
	* gdb.dwarf2/implref-global.c: Likewise.
	* gdb.dwarf2/implref-global.exp: Likewise.
	* gdb.dwarf2/implref-struct.c: Likewise.
	* gdb.dwarf2/implref-struct.exp: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sh: make constant unsigned to avoid narrowing
@ 2016-06-01  3:22 sergiodj+buildbot
  2016-06-01  4:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  3:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2b5fccc630a7cb7e1c241e5249bf6e8917d917d ***

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

sh: make constant unsigned to avoid narrowing

Shifting into the sign bit of a 32 bit int and then converting to a unsigned
type is less straight forward than just shifting an unsigned value.

opcodes/ChangeLog:

2016-05-31  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* sh-opc.h (ARCH_SH_HAS_DSP): Make the shifted value an unsigned
	constant.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Wake up interruptible_select in remote_fileio ctrl-c handler
@ 2016-06-01  8:46 sergiodj+buildbot
  2016-06-01  9:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  8:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03d73f1fd9d89d89bdd021cad26693e4f6abc07a ***

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

Wake up interruptible_select in remote_fileio ctrl-c handler

As reported in PR 19998, after type ctrl-c, GDB hang there and does
not send interrupt.  It causes a fail in gdb.base/interrupt.exp.
All targets support remote fileio should be affected.

When we type ctrc-c, SIGINT is handled by remote_fileio_sig_set,
as shown below,

 #0  remote_fileio_sig_set (sigint_func=0x4495d0 <remote_fileio_ctrl_c_signal_handler(int)>) at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:325
 #1  0x00000000004495de in remote_fileio_ctrl_c_signal_handler (signo=<optimised out>) at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:349
 #2  <signal handler called>
 #3  0x00007ffff647ed83 in __select_nocancel () at ../sysdeps/unix/syscall-template.S:81
 #4  0x00000000005530ce in interruptible_select (n=10, readfds=readfds@entry=0x7fffffffd730, writefds=writefds@entry=0x0, exceptfds=exceptfds@entry=0x0,
    timeout=timeout@entry=0x0) at /home/yao/SourceCode/gnu/gdb/git/gdb/event-top.c:1017
 #5  0x000000000061ab20 in stdio_file_read (file=<optimised out>, buf=0x12d02e0 "\n\022-\001", length_buf=16383)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/ui-file.c:577
 #6  0x000000000044a4dc in remote_fileio_func_read (buf=0x12c0360 "") at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:583
 #7  0x0000000000449598 in do_remote_fileio_request (uiout=<optimised out>, buf_arg=buf_arg@entry=0x12c0340)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:1179

we don't set quit_serial_event,

  do
    {
      res = gdb_select (n, readfds, writefds, exceptfds, timeout);
    }
  while (res == -1 && errno == EINTR);

  if (res == 1 && FD_ISSET (fd, readfds))
    {
      errno = EINTR;
      return -1;
    }
  return res;

we can't go out of the loop above, and that is why GDB can't send
interrupt.

Recently, we stop throwing exception from SIGINT handler
(remote_fileio_ctrl_c_signal_handler)
https://sourceware.org/ml/gdb-patches/2016-03/msg00372.html, which
is correct, because gdb_select is interruptible.  However, in the
same patch series, we add interruptible_select later as a wrapper
to gdb_select, https://sourceware.org/ml/gdb-patches/2016-03/msg00375.html
and it is not interruptible (because of the loop in it) unless
select/poll-able file descriptors are marked.

This fix in this patch is to call quit_serial_event_set, so that we can
go out of the loop above, return -1 and set errno to EINTR.

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

	PR remote/19998
	* remote-fileio.c (remote_fileio_ctrl_c_signal_handler): Call
	quit_serial_event_set.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] infcmd, btrace: fix crash in 'finish' for tailcall-only frames
@ 2016-06-01  9:27 sergiodj+buildbot
  2016-06-01 10:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  9:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3b5daf9f735999259c5a8f68b422850c59897e5 ***

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

infcmd, btrace: fix crash in 'finish' for tailcall-only frames

Patch 7eb895307f53 Skip unwritable frames in command "finish"
skips non-writable frames in addition to tailcall frames.

If skip_tailcall_frames already returns NULL, skip_unwritable_frames
will be called with a NULL frame and crash in get_frame_arch.  This is
caught by gdb.btrace/tailcall-only.exp.

Further, if we ever end up with a mixture of tailcall and non-writable
frames, we may not skip all of them, as intended.

Loop over skip_tailcall_frames and skip_unwritable_frames as long as at least
one of them makes progress.

gdb/
	* infcmd.c (skip_finish_frames): New.
	(finish_command): Call skip_finish_frames.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add xmalloc_failed() function to common-utils.c in to avoid the need to link in libiberty's xmalloc code.
@ 2016-06-01 10:56 sergiodj+buildbot
  2016-06-01 11:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-01 10:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51403f74d96cc69f391fbd31389a9153a230b431 ***

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

Add xmalloc_failed() function to common-utils.c in to avoid the need to link in libiberty's xmalloc code.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for some variants of the ARC nps400 rflt instruction.
@ 2016-06-01 15:39 sergiodj+buildbot
  2016-06-01 16:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-01 15:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 315f180f2f0a59af561180e4ed9387f4c7bada78 ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 315f180f2f0a59af561180e4ed9387f4c7bada78

Add support for some variants of the ARC nps400 rflt instruction.

gas     * testsuite/gas/arc/nps-400-1.s: Add rflt variants with
        operands of types a,b,u6, 0,b,u6, and 0,b,limm.
        * testsuite/gas/arc/nps-400-1.d: Likewise.

opcodes * arc-nps400-tbl.h: Add operands a,b,u6, 0,b,u6, and
        0,b,limm to the rflt instruction.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb/remote-fileio.c: Eliminate custom SIGINT signal handler
@ 2016-06-01 15:48 sergiodj+buildbot
  2016-06-01 17:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-01 15:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb7c96deb1a14ef7e8b51d5339a65a8064515c78 ***

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

gdb/remote-fileio.c: Eliminate custom SIGINT signal handler

... and fix Ctrl-C races.

The current remote-fileio.c SIGINT/EINTR code can lose Ctrl-C --
there's a period where SIG_IGN is installed as signal handler, for
example.

Since:

 - remote.c no longer installs a custom SIGINT handler;

 - The current remote-fileio.c SIGINT handler is basically the same as
   the default SIGINT handler (event-top.c:handle_sigint), in
   principle, except that instead of setting the quit flag, it sets a
   separate flag.

I think we should be able to completely remove the remote-fileio.c
SIGINT handler, and centralize on the quit flag, thus fixing the
Ctrl-C race.

gdb/ChangeLog:
yyyy-mm-dd  Pedro Alves  <palves@redhat.com>

	* remote-fileio.c (remote_fio_ctrl_c_flag, remote_fio_sa)
	(remote_fio_osa)
	(remote_fio_ofunc, remote_fileio_sig_init, remote_fileio_sig_set)
	(remote_fileio_sig_exit, remote_fileio_ctrl_c_signal_handler):
	Delete.
	(remote_fileio_o_quit_handler): New global.
	(remote_fileio_quit_handler): New function.
	(remote_fileio_reply): Check the quit flag instead of the custom
	'remote_fio_ctrl_c_flag' flag.  Restore the quit handler instead
	of changing the SIGINT handler.
	(do_remote_fileio_request): Override the quit handler instead of
	changing the SIGINT handler.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add new Serbian translation for the bfd library.
@ 2016-06-01 16:03 sergiodj+buildbot
  2016-06-01 18:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-01 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 885a10879eea3cf7ccbb324109a56f0bc391dcfa ***

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

Add new Serbian translation for the bfd library.

	* po/sr.po: New Serbian translation.
	* configure.ac (ALL_LINGUAS): Add sr.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] add more extern C
@ 2016-06-02  1:33 sergiodj+buildbot
  2016-06-02  2:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-02  1:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1fe0971e41a4097610862acabf54a896695fe834 ***

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

add more extern C

opcodes/ChangeLog:

2016-06-01  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* nds32-asm.h: Add extern "C".
	* sh-opc.h: Likewise.

bfd/ChangeLog:

2016-06-01  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf32-hppa.h: Add extern "C".
	* elf32-nds32.h: Likewise.
	* elf32-tic6x.h: Likewise.

include/ChangeLog:

2016-06-01  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf/mips.h: Likewise.
	* elf/sh.h: Likewise.
	* opcode/d10v.h: Likewise.
	* opcode/d30v.h: Likewise.
	* opcode/ia64.h: Likewise.
	* opcode/mips.h: Likewise.
	* opcode/ppc.h: Likewise.
	* opcode/sparc.h: Likewise.
	* opcode/tic6x.h: Likewise.
	* opcode/v850.h: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Revert PR16467 change
@ 2016-06-02  3:32 sergiodj+buildbot
  2016-06-02  4:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-02  3:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b677558bc6c7b2477bb33c709e6017e68e7ae8c ***

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

Revert PR16467 change

This reverts the pr16467 change, which was incorrect due to faulty
analysis of the pr16467 testcase.  The failure was not due to a
mismatch in symbol type (ifunc/non-ifunc) but due to a symbol loop
being set up.

See https://sourceware.org/ml/binutils/2016-06/msg00013.html for some
rambling on versioned symbols and ELF shared library symbol overriding
that explain this patch.

bfd/
	PR ld/20159
	PR ld/16467
	* elflink.c (_bfd_elf_merge_symbol): Revert PR16467 change.
	(_bfd_elf_add_default_symbol): Don't indirect to/from defined
	symbol given a version by a script different to the version
	of the symbol being added.
	(elf_link_add_object_symbols): Use _bfd_elf_strtab_save and
	_bfd_elf_strtab_restore.  Don't fudge dynstr references.
	* elf-strtab.c (_bfd_elf_strtab_restore_size): Delete.
	(struct strtab_save): New.
	(_bfd_elf_strtab_save, _bfd_elf_strtab_restore): New functions.
	* elf-bfd.h (_bfd_elf_strtab_restore_size): Delete.
	(_bfd_elf_strtab_save, _bfd_elf_strtab_restore): Declare.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for 48 and 64 bit ARC instructions.
@ 2016-06-02 13:17 sergiodj+buildbot
  2016-06-02 13:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4eb6f892502bad1ec4e1828d0140959bb004a3b6 ***

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

Add support for 48 and 64 bit ARC instructions.

gas	* config/tc-arc.c (parse_opcode_flags): New function.
	(find_opcode_match): Move flag parsing code out to new function.
	Ignore operands marked IGNORE.
	(build_fake_opcode_hash_entry): New function.
	(find_special_case_long_opcode): New function.
	(find_special_case): Lookup long opcodes.
	* testsuite/gas/arc/nps400-7.d: New file.
	* testsuite/gas/arc/nps400-7.s: New file.

include	* opcode/arc.h (MAX_INSN_ARGS): Increase to 16.
	(struct arc_long_opcode): New structure.
	(arc_long_opcodes): Declare.
	(arc_num_long_opcodes): Declare.

opcodes	* arc-dis.c (struct arc_operand_iterator): New structure.
	(find_format_from_table): All the old content from find_format,
	with some minor adjustments, and parameter renaming.
	(find_format_long_instructions): New function.
	(find_format): Rewritten.
	(arc_insn_length): Add LSB parameter.
	(extract_operand_value): New function.
	(operand_iterator_next): New function.
	(print_insn_arc): Use new functions to find opcode, and iterator
	over operands.
	* arc-opc.c (insert_nps_3bit_dst_short): New function.
	(extract_nps_3bit_dst_short): New function.
	(insert_nps_3bit_src2_short): New function.
	(extract_nps_3bit_src2_short): New function.
	(insert_nps_bitop1_size): New function.
	(extract_nps_bitop1_size): New function.
	(insert_nps_bitop2_size): New function.
	(extract_nps_bitop2_size): New function.
	(insert_nps_bitop_mod4_msb): New function.
	(extract_nps_bitop_mod4_msb): New function.
	(insert_nps_bitop_mod4_lsb): New function.
	(extract_nps_bitop_mod4_lsb): New function.
	(insert_nps_bitop_dst_pos3_pos4): New function.
	(extract_nps_bitop_dst_pos3_pos4): New function.
	(insert_nps_bitop_ins_ext): New function.
	(extract_nps_bitop_ins_ext): New function.
	(arc_operands): Add new operands.
	(arc_long_opcodes): New global array.
	(arc_num_long_opcodes): New global.
	* arc-nps400-tbl.h: Add comments referencing arc_long_opcodes.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Replace data32 with data16 in comments
@ 2016-06-02 14:30 sergiodj+buildbot
  2016-06-02 15:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 14:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ddf1bdd423a127564d5d13cabde8863431576a3 ***

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

Replace data32 with data16 in comments

The 0x66 prefix is data16, not data32 in 64-bit.

	* elf64-x86-64.c: Replace data32 with data16 in comments.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Allow ARC Linux targets that do not use uclibc.
@ 2016-06-02 15:31 sergiodj+buildbot
  2016-06-02 16:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 15:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ad0bb5f3a5b2d03079819cf419b174a762c2d52 ***

Author: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Branch: master
Commit: 4ad0bb5f3a5b2d03079819cf419b174a762c2d52

Allow ARC Linux targets that do not use uclibc.

bfd    * config.bfd: Replace -uclibc with *.

gas    * configure.tgt: Replace -uclibc with *.

ld     * configure.tgt: Replace -uclibc with *.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add "arm_any" architecture type to allow -m option to various binutils to match any ARM architecture.
@ 2016-06-02 16:28 sergiodj+buildbot
  2016-06-02 18:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99914dfd71d74bc700bb6d15647895ac0c8cc8e1 ***

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

Add "arm_any" architecture type to allow -m option to various binutils to match any ARM architecture.

	PR target/20088
	* cpu-arm.c (processors): Add "arm_any" type to match any ARM
	architecture.
	(arch_info_struct): Likewise.
	(architectures): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR python/18984
@ 2016-06-02 19:39 sergiodj+buildbot
  2016-06-02 20:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 19:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b40ec0559f4b24ccdf6b073610c526c4aa33c4d ***

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

Fix PR python/18984

This fixes PR python/18984.

The bug is that gdbpy_solib_name uses GDB_PY_LL_ARG, whereas it should
use GDB_PY_LLU_ARG to avoid overflow.

Built and tested on x86-64 Fedora 23.

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

	PR python/18984:
	* python/python.c (gdbpy_solib_name): Use GDB_PY_LLU_ARG.

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

	PR python/18984:
	* gdb.python/py-shared.exp: Add solib_name test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix C++ build for Cygwin
@ 2016-06-03 11:47 sergiodj+buildbot
  2016-06-03 13:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-03 11:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ae534d2cfef358bcde3166ce3a29faf85bc632a ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 0ae534d2cfef358bcde3166ce3a29faf85bc632a

Fix C++ build for Cygwin

gdb/ChangeLog:

2016-06-02  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (handle_output_debug_string): Return type of
	gdb_signal_from_host() is gdb_signal, not an int.
	(windows_get_exec_module_filename): Add pointer casts for C++.

gdb/gdbserver/ChangeLog:

2016-06-02  Jon Turney  <jon.turney@dronecode.org.uk>

	* win32-low.c (win32_create_inferior): Add pointer casts for C++.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Handle indirect branches for AMD64 and Intel64
@ 2016-06-03 23:15 sergiodj+buildbot
  2016-06-04  0:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-03 23:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07f5af7d3c635234284e7a0f7dd7a410b1628b8b ***

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

Handle indirect branches for AMD64 and Intel64

AMD64 spec and Intel64 spec differ in indirect branches in 64-bit mode.
AMD64 supports indirect branches with 16-bit address via the data size
prefix while the data size prefix is ignored by Intel64.

gas/

	PR binutis/18386
	* testsuite/gas/i386/i386.exp: Run x86-64-branch-4.
	* testsuite/gas/i386/x86-64-branch.d: Updated.
	* testsuite/gas/i386/ilp32/x86-64-branch.d: Likewise.
	* testsuite/gas/i386/x86-64-branch-4.l: New file.
	* testsuite/gas/i386/x86-64-branch-4.s: Likewise.

opcodes/

	PR binutis/18386
	* i386-dis.c (indirEv): Replace stack_v_mode with indir_v_mode.
	(indir_v_mode): New.
	Add comments for '&'.
	(reg_table): Replace "{T|}" with "{&|}" on call and jmp.
	(putop): Handle '&'.
	(intel_operand_size): Handle indir_v_mode.
	(OP_E_register): Likewise.
	* i386-opc.tbl: Mark 64-bit indirect call/jmp as AMD64.  Add
	64-bit indirect call/jmp for AMD64.
	* i386-tbl.h: Regenerated


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Re-add support for lbarx, lharx, stbcx. and sthcx. insns back to the E6500 cpu.
@ 2016-06-03 23:50 sergiodj+buildbot
  2016-06-04  1:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-03 23:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 026122a670440bc51266f8e013e5c5877c19b54e ***

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

Re-add support for lbarx, lharx, stbcx. and sthcx. insns back to the E6500 cpu.

opcodes/
	PR binutils/20196
	* ppc-opc.c (powerpc_opcodes <lbarx, lharx, stbcx., sthcx.>): Enable
	opcodes for E6500.

gas/
	PR binutils/20196
	* gas/testsuite/gas/ppc/e6500.s <lbarx, lharx, lwarx, ldarx,
	stbcx., sthcx., stwcx., stdcx.>: Add tests.
	* gas/testsuite/gas/ppc/e6500.d: Likewise.
	* gas/testsuite/gas/ppc/power8.s: Likewise.
	* gas/testsuite/gas/ppc/power8.d: Likewise.
	* gas/testsuite/gas/ppc/power4.s <lwarx, ldarx, stwcx.,
	stdcx.>: Add tests.
	* gas/testsuite/gas/ppc/power4.d: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add z8k ld testsuite and fix range check in coff-z8k.c
@ 2016-06-04 20:35 sergiodj+buildbot
  2016-06-04 21:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-04 20:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ac27cd3c16ad828f96991f8f7b83a4bc10cae6c ***

Author: Christian Groessler <chris@groessler.org>
Branch: master
Commit: 2ac27cd3c16ad828f96991f8f7b83a4bc10cae6c

Add z8k ld testsuite and fix range check in coff-z8k.c

bfd/
	* coff-z8k.c (extra_case): Fix range check for R_JR relocation.

ld/
	* ld/testsuite/ld-z8k/0filler.s: New file.
	* ld/testsuite/ld-z8k/branch-target.s: New file.
	* ld/testsuite/ld-z8k/branch-target2.s: New file.
	* ld/testsuite/ld-z8k/calr-back-8001.d: New file.
	* ld/testsuite/ld-z8k/calr-back-8002.d: New file.
	* ld/testsuite/ld-z8k/calr-back-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/calr-back-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/calr-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/calr-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/calr-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/calr-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/calr-opcode.s: New file.
	* ld/testsuite/ld-z8k/dbjnz-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/dbjnz-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/dbjnz-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/dbjnz-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/dbjnz-opcode.s: New file.
	* ld/testsuite/ld-z8k/djnz-back-8001.d: New file.
	* ld/testsuite/ld-z8k/djnz-back-8002.d: New file.
	* ld/testsuite/ld-z8k/djnz-back-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/djnz-back-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/djnz-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/djnz-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/djnz-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/djnz-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/djnz-opcode.s: New file.
	* ld/testsuite/ld-z8k/filler.s: New file.
	* ld/testsuite/ld-z8k/jr-back-8001.d: New file.
	* ld/testsuite/ld-z8k/jr-back-8002.d: New file.
	* ld/testsuite/ld-z8k/jr-back-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/jr-back-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/jr-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/jr-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/jr-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/jr-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/jr-opcode.s: New file.
	* ld/testsuite/ld-z8k/ldr-back-8001.d: New file.
	* ld/testsuite/ld-z8k/ldr-back-8002.d: New file.
	* ld/testsuite/ld-z8k/ldr-back-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/ldr-back-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/ldr-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/ldr-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/ldr-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/ldr-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/ldr-opcode.s: New file.
	* ld/testsuite/ld-z8k/ldrb-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/ldrb-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/ldrb-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/ldrb-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/ldrb-opcode.s: New file.
	* ld/testsuite/ld-z8k/ldrb-opcode2.s: New file.
	* ld/testsuite/ld-z8k/other-file.s: New file.
	* ld/testsuite/ld-z8k/reloc.dd: New file.
	* ld/testsuite/ld-z8k/reloc.ld: New file.
	* ld/testsuite/ld-z8k/relocseg.dd: New file.
	* ld/testsuite/ld-z8k/relocseg.ld: New file.
	* ld/testsuite/ld-z8k/relocseg1.dd: New file.
	* ld/testsuite/ld-z8k/test-ld.sh: New file.
	* ld/testsuite/ld-z8k/this-file.s: New file.
	* ld/testsuite/ld-z8k/z8k.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Support x86-64 TLS code sequences without PLT
@ 2016-06-06 18:25 sergiodj+buildbot
  2016-06-06 20:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-06 18:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e2cbcd9156d1606a9f2153aecd93a89fe6e29180 ***

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

Support x86-64 TLS code sequences without PLT

We can generate x86-64 TLS code sequences for general and local dynamic
models without PLT, which uses indirect call via GOT:

call *__tls_get_addr@GOTPCREL(%rip)

instead of direct call:

call __tls_get_addr[@PLT]

Since direct call is 4-byte long and indirect call, is 5-byte long, the
extra one byte must be handled properly.

For general dynamic model, one 0x66 prefix before call instruction is
removed to make room for indirect call.  For local dynamic model, we
simply use 5-byte indirect call.

TLS linker optimization is updated to recognize new instruction patterns.
For local dynamic model to local exec model transition, we generate
4 0x66 prefixes, instead of 3, before mov instruction in 64-bit and
generate a 5-byte nop, instead of 4-byte, before mov instruction in
32-bit.  Since linker may convert

call *__tls_get_addr@GOTPCREL(%rip)

to

addr32 call __tls_get_addr

when producing static executable, both patterns are recognized.

bfd/

	* elf64-x86-64.c (elf_x86_64_link_hash_entry): Add tls_get_addr.
	(elf_x86_64_link_hash_newfunc): Initialize tls_get_addr to 2.
	(elf_x86_64_check_tls_transition): Check indirect call and
	direct call with the addr32 prefix for general and local dynamic
	models.  Set the tls_get_addr feild.
	(elf_x86_64_convert_load_reloc): Always use addr32 prefix for
	indirect __tls_get_addr call via GOT.
	(elf_x86_64_relocate_section): Handle GD->LE, GD->IE and LD->LE
	transitions with indirect call and direct call with the addr32
	prefix.

ld/

	* testsuite/ld-x86-64/pass.out: New file.
	* testsuite/ld-x86-64/tls-def1.c: Likewise.
	* testsuite/ld-x86-64/tls-gd1.S: Likewise.
	* testsuite/ld-x86-64/tls-ld1.S: Likewise.
	* testsuite/ld-x86-64/tls-main1.c: Likewise.
	* testsuite/ld-x86-64/tls.exp: Likewise.
	* testsuite/ld-x86-64/tlsbin2-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsbin2.dd: Likewise.
	* testsuite/ld-x86-64/tlsbin2.rd: Likewise.
	* testsuite/ld-x86-64/tlsbin2.sd: Likewise.
	* testsuite/ld-x86-64/tlsbin2.td: Likewise.
	* testsuite/ld-x86-64/tlsbinpic2.s: Likewise.
	* testsuite/ld-x86-64/tlsgd10.dd: Likewise.
	* testsuite/ld-x86-64/tlsgd10.s: Likewise.
	* testsuite/ld-x86-64/tlsgd11.dd: Likewise.
	* testsuite/ld-x86-64/tlsgd11.s: Likewise.
	* testsuite/ld-x86-64/tlsgd12.d: Likewise.
	* testsuite/ld-x86-64/tlsgd12.s: Likewise.
	* testsuite/ld-x86-64/tlsgd13.d: Likewise.
	* testsuite/ld-x86-64/tlsgd13.s: Likewise.
	* testsuite/ld-x86-64/tlsgd14.dd: Likewise.
	* testsuite/ld-x86-64/tlsgd14.s: Likewise.
	* testsuite/ld-x86-64/tlsgd5c.s: Likewise.
	* testsuite/ld-x86-64/tlsgd6c.s: Likewise.
	* testsuite/ld-x86-64/tlsgd9.dd: Likewise.
	* testsuite/ld-x86-64/tlsgd9.s: Likewise.
	* testsuite/ld-x86-64/tlsld4.dd: Likewise.
	* testsuite/ld-x86-64/tlsld4.s: Likewise.
	* testsuite/ld-x86-64/tlsld5.dd: Likewise.
	* testsuite/ld-x86-64/tlsld5.s: Likewise.
	* testsuite/ld-x86-64/tlsld6.dd: Likewise.
	* testsuite/ld-x86-64/tlsld6.s: Likewise.
	* testsuite/ld-x86-64/tlspic2-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlspic2.dd: Likewise.
	* testsuite/ld-x86-64/tlspic2.rd: Likewise.
	* testsuite/ld-x86-64/tlspic2.sd: Likewise.
	* testsuite/ld-x86-64/tlspic2.td: Likewise.
	* testsuite/ld-x86-64/tlspic3.s: Likewise.
	* testsuite/ld-x86-64/tlspie2.s: Likewise.
	* testsuite/ld-x86-64/tlspie2a.d: Likewise.
	* testsuite/ld-x86-64/tlspie2b.d: Likewise.
	* testsuite/ld-x86-64/tlspie2c.d: Likewise.
	* testsuite/ld-x86-64/tlsgd5.dd: Updated.
	* testsuite/ld-x86-64/tlsgd6.dd: Likewise.
	* testsuite/ld-x86-64/x86-64.exp: Run libtlspic2.so, tlsbin2,
	tlsgd5b, tlsgd6b, tlsld4, tlsld5, tlsld6, tlsgd9, tlsgd10,
	tlsgd11, tlsgd14, tlsgd12, tlsgd13, tlspie2a, tlspie2b and
	tlspie2c.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add method/format information to =record-started
@ 2016-06-06 21:21 sergiodj+buildbot
  2016-06-06 22:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-06 21:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 38b022b4452f996fb5a8598f80d850b594621bcf ***

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

Add method/format information to =record-started

Eclipse CDT now supports enabling execution recording using two methods
(full and btrace) and both formats for btrace (bts and pt).  In the
event that recording is enabled behind the back of the GUI (by the user
on the command line, or a script), we need to know which method/format
are being used, so it can be correctly reflected in the interface.  This
patch adds this information to the =record-started async record.

Before:

  =record-started,thread-group="i1"

After:

  =record-started,thread-group="i1",method="btrace",format="bts"
  =record-started,thread-group="i1",method="btrace",format="pt"
  =record-started,thread-group="i1",method="full"

The "format" field is only present when the current method supports
multiple formats (only the btrace method as of now).

gdb/ChangeLog:

	* NEWS: Mention the new fields in =record-started.
	* common/btrace-common.h (btrace_format_short_string): New function
	declaration.
	* common/btrace-common.c (btrace_format_short_string): New
	function.
	* mi/mi-interp.c (mi_record_changed): Output method and format
	fields in the =record-started record.
	* record-btrace.c (record_btrace_open): Adapt record_changed
	notification.
	* record-full.c (record_full_open): Likewise.
	* record.c (cmd_record_stop): Likewise.

gdb/doc/ChangeLog:

	* gdb.texinfo (GDB/MI Async Records): Document method and
	format fields in =record-started.
	* observer.texi (record_changed): Add method and format
	parameters.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-record-changed.exp: Adjust =record-started output
	matching.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] Add command line option for RAS extension.
@ 2016-06-07  9:09 sergiodj+buildbot
  2016-06-07 11:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-07  9:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d1464f294405a064d84e3d4f15c1ceff3639add ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 4d1464f294405a064d84e3d4f15c1ceff3639add

[ARM] Add command line option for RAS extension.

This patch adds the architecture extension "+ras" to enable RAS
support. It is enabled by default for -march=armv8.2-a and available but
disabled by default for armv8-a and armv8.1-a.

gas/
	* config/tc-arm.c (arm_ext_v8_2): Rename to arm_ext_ras.
	(arm_ext_ras): Renamed from arm_ext_v8_2.
	(insns): Update for arm_ext_v8_2 renaming.
	(arm_extensions): Add "ras".
	* doc/c-arm.texi (ARM Options): Add an entry for "ras".
	* testsuite/gas/arm/armv8-a+ras.d: New.
	* testsuite/gas/arm/armv8_2-a.d: Add explicit command line
	options.

include/
	* opcode/arm.h (ARM_EXT2_RAS): New.  Also align preceding
	entries.
	(ARM_AEXT_V8_2A): Add ARM_EXT2_RAS.

opcodes/
	* arm-dis.c (arm_opcodes): Replace ARM_EXT_V8_2A with
	ARM_EXT_RAS in relevant entries.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Frame static link: Handle null pointer.
@ 2016-06-07 11:49 sergiodj+buildbot
  2016-06-07 13:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-07 11:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2091da296fd563f62d856dcb5a049a63484ed65e ***

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

Frame static link: Handle null pointer.

2016-06-07  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* findvar.c (follow_static_link): Check for valid pointer.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PowerPC VLE
@ 2016-06-07 13:02 sergiodj+buildbot
  2016-06-07 16:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-07 13:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14b57c7c6a53c747a8819fed3da858eae4195a0e ***

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

PowerPC VLE

VLE is an encoding, not a particular processor architecture, so it
isn't really proper to select insns based on PPC_OPCODE_VLE.  For
example
{"evaddw",  VX (4, 512), VX_MASK, PPCSPE|PPCVLE, PPCNONE, {RS, RA, RB}},
{"vaddubs", VX (4, 512), VX_MASK, PPCVEC|PPCVLE, PPCNONE, {VD, VA, VB}},
shows two insns that have the same encoding, both available with VLE.
Enabling both with VLE means we can't disassemble the second variant
even if -Maltivec is given rather than -Mspe.  Also, we don't check
user assembly against the processor type as well as we could.

Another problem is that when using the VLE encoding, insns from the
main ppc opcode table are not available, except those using opcode 4
and 31.  Correcting this revealed two errors in the ld testsuite,
use of "nop" and "rfmci" when -mvle.

This patch fixes those problems in the opcode table, and removes
PPCNONE.  I find a plain 0 distracts less from other values.

In addition, I've implemented code to recognize some machine values
from the apuinfo note present in ppc32 objects.  It's not a complete
disambiguation since we're lacking info to detect newer chips, but
what we have should help with disassembly.

include/
	* elf/ppc.h (APUINFO_SECTION_NAME, APUINFO_LABEL, PPC_APUINFO_ISEL,
	PPC_APUINFO_PMR, PPC_APUINFO_RFMCI, PPC_APUINFO_CACHELCK,
	PPC_APUINFO_SPE, PPC_APUINFO_EFS, PPC_APUINFO_BRLOCK,
	PPC_APUINFO_VLE: Define.
opcodes/
	* ppc-dis.c (ppc_opts): Delete extraneous parentheses.  Default
	cpu for "vle" to e500.
	* ppc-opc.c (ALLOW8_SPRG): Remove PPC_OPCODE_VLE.
	(NO371, PPCSPE, PPCISEL, PPCEFS, MULHW, DCBT_EO): Likewise.
	(PPCNONE): Delete, substitute throughout.
	(powerpc_opcodes): Remove PPCVLE from "flags".  Add to "deprecated"
	except for major opcode 4 and 31.
	(vle_opcodes <se_rfmci>): Add PPCRFMCI to flags.
bfd/
	* cpu-powerpc.c (powerpc_compatible): Allow bfd_mach_ppc_vle entry
	to match other 32-bit archs.
	* elf32-ppc.c (_bfd_elf_ppc_set_arch): New function.
	(ppc_elf_object_p): Call it.
	(ppc_elf_special_sections): Use APUINFO_SECTION_NAME.  Fix
	overlong line.
	(APUINFO_SECTION_NAME, APUINFO_LABEL): Don't define here.
	* elf64-ppc.c (ppc64_elf_object_p): Call _bfd_elf_ppc_set_arch.
	* bfd-in.h (_bfd_elf_ppc_at_tls_transform,
	_bfd_elf_ppc_at_tprel_transform): Move to..
	* elf-bfd.h: ..here.
	(_bfd_elf_ppc_set_arch): Declare.
	* bfd-in2.h: Regenerate.
gas/
	* config/tc-ppc.c (PPC_APUINFO_ISEL, PPC_APUINFO_PMR,
	PPC_APUINFO_RFMCI, PPC_APUINFO_CACHELCK, PPC_APUINFO_SPE,
	PPC_APUINFO_EFS, PPC_APUINFO_BRLOCK, PPC_APUINFO_VLE): Don't define.
	(ppc_setup_opcodes): Check vle disables powerpc_opcodes overridden
	by vle_opcodes, and that vle flag doesn't enable opcodes.  Don't
	add vle_opcodes twice.
	(ppc_cleanup): Use APUINFO_SECTION_NAME and APUINFO_LABEL.
ld/
	* testsuite/ld-powerpc/apuinfo1.s: Delete nop.
	* testsuite/ld-powerpc/apuinfo-vle2.s: New.
	* testsuite/ld-powerpc/powerpc.exp: Use apuinfo-vle2.s.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARC] Generate DT_RELACOUNT.
@ 2016-06-13 14:52 sergiodj+buildbot
  2016-06-13 17:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-13 14:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f7f3789ca97ecaf0c4169c6d82e205f69fa0580 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 0f7f3789ca97ecaf0c4169c6d82e205f69fa0580

[ARC] Generate DT_RELACOUNT.

bfd/
2016-06-13  Cupertino Miranda  <cmiranda@synospsy.com>

	* elf32-arc.c (elf32_arc_reloc_type_class): Defined function to
	enable support for "-z combreloc" and DT_RELACOUNT.
	(elf_backend_reloc_type_class): Likewise


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Push thread->control.command_interp to the struct thread_fsm
@ 2016-06-21 15:18 sergiodj+buildbot
  2016-06-23  7:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 15:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8980e177bb62ec64875b335cf8733b41f3aae2fd ***

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

Push thread->control.command_interp to the struct thread_fsm

I noticed that if we step into an inline function, step_1 never
reaches proceed, and thus nevers sets the thread's
tp->control.command_interp.  Because of that,
should_print_stop_to_console fails to determine that is should print
stop output to the console.

The fix is to set the thread's command_interp earlier.  However, I
realized that we can move that field to the thread_fsm, given that its
lifetime is exactly the same as thread_fsm.  So the patch plumbs all
fsms constructors to take the command interp and store it in the
thread_fsm.

We can see the fix in action, with e.g., the gdb.opt/inline-cmds.exp
test, and issuing a step when stopped at line 67:

 &"s\n"
 ^running
 *running,thread-id="all"
 (gdb)
 ~"67\t  result = func2 ();\n"
 *stopped,reason="end-stepping-range",frame={addr="0x00000000004004d0",func="main",args=[],file="/home/pedro/gdb/mygit/src/gdb/testsuite/gdb.opt/inline-cmds.c",fullname="/home/pedro/gdb/mygit/src/gdb/testsuite/gdb.opt/inline-cmds.c",line="67"},thread-id="1",stopped-threads="all",core="0"
 (gdb)
 s
 &"s\n"
 ^running
 *running,thread-id="all"
 (gdb)
+ ~"func2 () at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.opt/inline-cmds.c:67\n"
+ ~"67\t  result = func2 ();\n"
 *stopped,reason="end-stepping-range",frame={addr="0x00000000004004d0",func="func2",args=[],file="/home/pedro/gdb/mygit/src/gdb/testsuite/gdb.opt/inline-cmds.c",fullname="/home/pedro/gdb/mygit/src/gdb/testsuite/gdb.opt/inline-cmds.c",line="67"},thread-id="1",stopped-threads="all",core="0"
 (gdb)

(The inline-cmds.exp command is adjusted to exercise this.)

(Due to the follow_fork change, this also fixes "next N" across a fork
with "set follow-fork child" with "set detach-on-fork on".  Commands
that rely on internal breakpoints, like "finish" will still require
more work to migrate breakpoints etc. to the child thread.)

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

	* breakpoint.c (new_until_break_fsm): Add 'cmd_interp' parameter.
	(until_break_fsm_should_stop, until_break_fsm_clean_up): Add
	thread parameter.
	(until_break_command): Pass command interpreter to thread fsm
	ctor.
	* cli/cli-interp.c (should_print_stop_to_console): Adjust.
	* gdbthread.h (struct thread_control_state) <command_interp>:
	Delete field.
	* infcall.c (new_call_thread_fsm): Add 'cmd_interp' parameter.
	Pass it down.
	(call_thread_fsm_should_stop): Add thread parameter.
	(call_function_by_hand_dummy): Pass command interpreter to thread
	fsm ctor.  Pass thread pointer to fsm clean up method.
	* infcmd.c: Include interps.h.
	(struct step_command_fsm) <thread>: Delete field.
	(new_step_command_fsm): Add 'cmd_interp' parameter.  Pass it down.
	(step_command_fsm_prepare): Remove references to fsm's thread
	field.
	(step_1): Pass command interpreter to thread
	fsm ctor.  Pass thread pointer to fsm clean up method.
	(step_command_fsm_should_stop, step_command_fsm_clean_up): Add
	thread parameter and use it.
	(new_until_next_fsm): Add 'cmd_interp' parameter.  Pass it down.
	(until_next_fsm_should_stop, until_next_fsm_clean_up): Add thread
	parameter and use it.
	(until_next_command): Pass command interpreter to thread fsm ctor.
	(struct finish_command_fsm) <thread>: Delete field.
	(finish_command_fsm_ops): Add NULL slot for should_notify_stop.
	(new_finish_command_fsm): Add 'cmd_interp' parameter and pass it
	down.  Remove thread parameter and adjust.
	(finish_command_fsm_should_stop, finish_command_fsm_clean_up): Add
	thread parameter and use it.
	(finish_command): Pass command interpreter to thread fsm ctor.
	Don't pass thread.
	* infrun.c (follow_fork): Move thread fsm to child fork instead of
	command interpreter, only.
	(clear_proceed_status_thread): Remove reference to command_interp.
	(proceed): Don't record the thread's command interpreter.
	(clean_up_just_stopped_threads_fsms): Pass thread to fsm clean_up
	method.
	(fetch_inferior_event): Pass thread to fsm should_stop method.
	* thread-fsm.c (thread_fsm_ctor): Add 'cmd_interp' parameter.
	Store it.
	(thread_fsm_clean_up, thread_fsm_should_stop): Add thread
	parameter and pass it down.
	* thread-fsm.h (struct thread_fsm) <command_interp>: New field.
	(struct thread_fsm_ops) <clean_up, should_stop>: Add thread
	parameter.
	(thread_fsm_ctor): Add 'cmd_interp' parameter.
	(thread_fsm_clean_up, thread_fsm_should_stop): Add thread
	parameter.
	* thread.c (thread_cancel_execution_command): Pass thread to
	thread fsm clean_up method.

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

	* gdb.opt/inline-cmds.c: Add "set mi break here" marker.
	* gdb.opt/inline-cmds.exp: Add MI tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Make main_ui be heap allocated
@ 2016-06-21 16:33 sergiodj+buildbot
  2016-06-23 11:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 16:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98d9f24ed15c5ca33bff06647d87b85e22e586d2 ***

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

Make main_ui be heap allocated

This is preparation for being able to create more than one UI object.

The change to gdb_main to stop using catch_errors is necessary because
catch_errors references current_uiout, which expands to
current_ui->m_current_ui, which would crash because current_ui is not
initialized yet at that point.  It didn't trigger earlier in the
series because before this patch, main_ui/current_ui always start out
non-NULL.

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

	* event-top.c (main_ui_): Delete.
	(main_ui, current_ui, ui_list): No longer initialize here.
	* main.c (captured_main): UI initialization code factored out to
	new new_ui function.
	(gdb_main): Wrap captured_main with TRY/CATCH instead of
	catch_errors.
	* top.c (highest_ui_num): New global.
	(new_ui): New function.
	* top.h (struct ui) <num>: New field.
	(new_ui): New declaration.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [DOC] Document support for running interpreters on separate UIs
@ 2016-06-21 19:51 sergiodj+buildbot
  2016-06-23 21:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 19:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86f78169c82095eced3a4d1b30f8e002ec841d79 ***

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

[DOC] Document support for running interpreters on separate UIs

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

	* NEWS: Mention support for running interpreters on separate
	UIs and the new new-ui command.

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

	* gdb.texinfo (Interpreters): Update intepreter-exec section,
	document new-ui and explain use case.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Send deleted watchpoint-scope output to all UIs
@ 2016-06-22 11:03 sergiodj+buildbot
  2016-06-24  2:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-22 11:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 468afe6c5fc9c80b8c175f3f13702ffaa6308400 ***

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

Send deleted watchpoint-scope output to all UIs

Testing with:

  make check RUNTESTFLAGS="SEPARATE_MI_TTY=1"

shows this, in gdb.mi/mi-watch.exp:

 -*stopped,reason="watchpoint-scope",wpnum="2",frame={addr="0x00000000004005cb",
 +*stopped,frame={addr="0x00000000004005cb",
 (...)
 -PASS: gdb.mi/mi-watch.exp: hw: watchpoint trigger
 +FAIL: gdb.mi/mi-watch.exp: hw: watchpoint trigger (unknown output after running)

That is, we lose the "watchpoint-scope" output on the MI UI.

This commit fixes it, and makes the test run with MI running as both
main UI and separate UI.

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

	* breakpoint.c (watchpoint_check): Send watchpoint-deleted output
	to all UIs.

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

	* gdb.mi/mi-watch.exp (test_watchpoint_creation_and_listing)
	(test_awatch_creation_and_listing)
	(test_rwatch_creation_and_listing, test_watchpoint_triggering):
	Remove 'type' parameter.
	(test_watchpoint_all): New parameter mi_mode.  Remove
	with_test_prefix.
	(top level): Use foreach_with_prefix, and add main/separate UI MI
	testing axis.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARC] Misc minor edits/fixes
@ 2016-06-23  9:16 sergiodj+buildbot
  2016-06-25  5:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-23  9:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce440d638d271d76cc491bd22dc34f6a5760140e ***

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

[ARC] Misc minor edits/fixes

The code supporting -mspfp, -mdpfp, and -mfpuda options are in
sections of code that are commented as being for backward
compatibility only, and having no effect. However, they do have an
effect, enabling the SPX, DPX, and DPA instruction subclasses
respectively. This commit moves the code supporting these options
away from the comments indicating that they are dummy options, and
also fixes a small issue where -mnps400 had the additional effect
of enabling SPX instructions.

A couple of other minor edits (that make no functional change) are
also included.

gas/ChangeLog:

        * config/tc-arc.c (options, md_longopts, md_parse_option):
        Move -mspfp, -mdpfp and -mfpuda out of the sections for
        dummy options. Correct erroneous enabling of SPFP
        instructions when using -mnps400.

include/ChangeLog:

        * opcode/arc.h: Make insn_class_t alphabetical again.

opcodes/ChangeLog:

        * arc-opc.c: Correct description of availability of NPS400
        features.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add elfcore_grok_freebsd_note to parse FreeBSD ELF core notes.
@ 2016-06-24 18:39 sergiodj+buildbot
  2016-06-26  3:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 18:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa1ed4a93a2eb0fb90d274c15288f3aad1791f60 ***

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

Add elfcore_grok_freebsd_note to parse FreeBSD ELF core notes.

Move parsing of FreeBSD-specific ELF core notes out of elfcore_grok_note
into a new elfcore_grok_freebsd_note function.  Add core note grok routines
for FreeBSD's psinfo and prstatus notes while here rather than depending
on the native handling in elfcore_grok_note.

bfd/ChangeLog:

	* elf.c (elfcore_grok_note): Remove handling of NT_X86_XSTATE for
	FreeBSD.  Remove case for NT_FREEBSD_THRMISC.
	(elfcore_grok_freebsd_psinfo): New function.
	(elfcore_grok_freebsd_prstatus): New function.
	(elfcore_grok_freebsd_note): New function.
	(elf_parse_notes): Use "elfcore_grok_freebsd_note" for "FreeBSD"
	notes.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] xtensa: prototype xtensa_make_property_section in elf/xtensa.h
@ 2016-06-25 16:01 sergiodj+buildbot
  2016-06-27  6:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-25 16:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c2c4aa12f4931fb79f94d787ef60e88960bb2a7 ***

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

xtensa: prototype xtensa_make_property_section in elf/xtensa.h

There's no reason to have multiple prototypes for the same function.

include/ChangeLog:

2016-06-25  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf/xtensa.h (xtensa_make_property_section): New prototype.

gas/ChangeLog:

2016-06-25  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* config/tc-xtensa.c (xtensa_make_property_section): Remove prototype.

bfd/ChangeLog:

2016-06-25  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf32-xtensa.c (xtensa_make_property_section): Remove prototype.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS16: Add R_MIPS16_PC16_S1 branch relocation support
@ 2016-06-28  0:55 sergiodj+buildbot
  2016-06-28  2:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-28  0:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c9775dde32773c57d4eb5dfb4265eda9cb8adbe8 ***

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

MIPS16: Add R_MIPS16_PC16_S1 branch relocation support

For R_MIPS16_PC16_S1 the calculation is `(sign_extend(A) + S - P) >> 1'
and the usual MIPS16 bit shuffling applies to relocated field handling,
as per the encoding of the branch target in the extended form of the
MIPS16 B, BEQZ, BNEZ, BTEQZ and BTNEZ instructions.

	include/
	* elf/mips.h (R_MIPS16_PC16_S1): New relocation.

	bfd/
	* elf32-mips.c (elf_mips16_howto_table_rel): Add
	R_MIPS16_PC16_S1.
	(mips16_reloc_map): Likewise.
	* elf64-mips.c (mips16_elf64_howto_table_rel): Likewise.
	(mips16_elf64_howto_table_rela): Likewise.
	(mips16_reloc_map): Likewise.
	* elfn32-mips.c (elf_mips16_howto_table_rel): Likewise.
	(elf_mips16_howto_table_rela): Likewise.
	(mips16_reloc_map): Likewise.
	* elfxx-mips.c (mips16_branch_reloc_p): New function.
	(mips16_reloc_p): Handle R_MIPS16_PC16_S1.
	(b_reloc_p): Likewise.
	(mips_elf_calculate_relocation): Likewise.
	(_bfd_mips_elf_check_relocs): Likewise.
	* reloc.c (BFD_RELOC_MIPS16_16_PCREL_S1): New relocation.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.

	gas/
	* config/tc-mips.c (mips16_reloc_p): Handle
	BFD_RELOC_MIPS16_16_PCREL_S1.
	(b_reloc_p): Likewise.
	(limited_pcrel_reloc_p): Likewise.
	(md_pcrel_from): Likewise.
	(md_apply_fix): Likewise.
	(tc_gen_reloc): Likewise.
	(md_convert_frag): Likewise.
	(mips_fix_adjustable): Update comment.
	* testsuite/gas/mips/mips16-branch-reloc-2.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-reloc-3.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-addend-2.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-addend-3.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-absolute.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-reloc-2.l: Remove file.
	* testsuite/gas/mips/mips16-branch-reloc-3.l: Remove file.
	* testsuite/gas/mips/mips16-branch-addend-2.l: Remove file.
	* testsuite/gas/mips/mips16-branch-addend-3.l: Remove file.
	* testsuite/gas/mips/mips16-branch-absolute.l: Remove file.
	* testsuite/gas/mips/mips16-branch-addend-2.s: Add padding.
	* testsuite/gas/mips/branch-weak.s: Adjust alignment, avoid
	implicit instruction padding, avoid MIPS16 JR->JRC conversion.
	* testsuite/gas/mips/branch-weak-6.d: New test.
	* testsuite/gas/mips/branch-weak-7.d: New test.
	* testsuite/gas/mips/mips.exp: Run the new tests.

	ld/
	* testsuite/ld-mips-elf/mips16-branch-2.d: New test.
	* testsuite/ld-mips-elf/mips16-branch-3.d: New test.
	* testsuite/ld-mips-elf/mips16-branch-addend-2.d: New test.
	* testsuite/ld-mips-elf/mips16-branch-addend-3.d: New test.
	* testsuite/ld-mips-elf/mips16-branch.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't convert R_SPARC_32 to R_SPARC_RELATIVE if class is ELFCLASS64.
@ 2016-06-28 11:18 sergiodj+buildbot
  2016-06-28 13:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 11:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7160c10d6530b79ea45d435933b07765f610f54d ***

Author: James Clarke <jrtc27@jrtc27.com>
Branch: master
Commit: 7160c10d6530b79ea45d435933b07765f610f54d

Don't convert R_SPARC_32 to R_SPARC_RELATIVE if class is ELFCLASS64.

bfd	* elfxx-sparc.c (_bfd_sparc_elf_relocate_section): Don't convert
	R_SPARC_32 to R_SPARC_RELATIVE if class is ELFCLASS64.

gold	* sparc.cc (Target_sparc::Scan::local): Don't convert R_SPARC_32
	to R_SPARC_RELATIVE if class is ELFCLASS64.
	(Target_sparc::Scan::global): Likewise.

ld	* testsuite/ld-elf/symbolic-func.r: Allow non-zero offsets from
	.text.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Probe catch syscall support
@ 2016-06-28 12:03 sergiodj+buildbot
  2016-06-28 15:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 12:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a31d2f068fa1384c505b540ea595d2d97813ba5f ***

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

Probe catch syscall support

In 82075af2c14b1f8a54fa5796fb63f7ef23f98d9d (Implement 'catch syscall'
for gdbserver), only x86 is supported, but the test can still be run
on other linux targets, like aarch64 and ppc, with native-gdbserver.
This causes many new fails.

This patch removes the check on isnative and on target triplets.
Instead, we can insert catch point, and resume the program to see whether
catch syscall is supported or not.

gdb/testsuite:

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

	* gdb.base/catch-syscall.exp: Remove check on isnative and target
	triplets.  Start gdb, execute catch syscall, and continue.  Check
	gdb's output to determine catch syscall is supported.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove parameter sysret from linux_target_ops.get_syscall_trapinfo
@ 2016-06-28 13:01 sergiodj+buildbot
  2016-06-28 18:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 13:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4cc32bec04aadc5c070d0f4aee656313a4854c11 ***

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

Remove parameter sysret from linux_target_ops.get_syscall_trapinfo

When I implement linux_target_ops.get_syscall_trapinfo for aarch64 and arm,
I find the second parameter sysret isn't used at all.  In RSP, we don't
need syscall return value either, because GDB can figure out the return
value from registers content got by 'g' packet.

This patch is to remove them.

gdb/gdbserver:

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

	* linux-low.c (get_syscall_trapinfo): Remove parameter sysret.
	Callers updated.
	* linux-low.h (struct linux_target_ops) <get_syscall_trapinfo>:
	Remove parameter sysno.
	* linux-x86-low.c (x86_get_syscall_trapinfo): Remove parameter
	sysret.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Use int64_t for address offset
@ 2016-06-28 17:17 sergiodj+buildbot
  2016-06-29  6:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ac09a5bbbff78d363ede2f038c31a9b1cb0887b ***

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

[AArch64] Use int64_t for address offset

In AArch64 displaced stepping and fast tracepoint, GDB/GDBserver needs
to check whether the offset can fit in the range.  We are using int32_t
for offset, it is sufficient to get an offset from an instruction, but
it is not enough to get an offset from two addresses.  For example,
we have a BL in shared lib which is at 0x0000002000040774, and the
scratch pad for displaced stepping is at 0x400698.  The offset can't
fit in 28 bit imm.  However, since we are using int32_t for offset, GDB
thinks the offset can fit it, and generate the B instruction with wrong
offset.

It fixes the following fail,

-FAIL: gdb.base/dso2dso.exp: next over call to sub2

gdb:

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

	* aarch64-tdep.c (aarch64_displaced_step_b): Use int64_t for
	variable new_offset.

gdb/gdbserver:

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

	* linux-aarch64-low.c (aarch64_ftrace_insn_reloc_b): Use int64_t
	for variable new_offset.
	(aarch64_ftrace_insn_reloc_b_cond): Likewise.
	(aarch64_ftrace_insn_reloc_cb): Likewise.
	(aarch64_ftrace_insn_reloc_tb): Likewise.
	(aarch64_install_fast_tracepoint_jump_pad): Likewise.  Use
	PRIx64 instead of PRIx32.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [TILEPro] Don't build gdb
@ 2016-06-28 18:34 sergiodj+buildbot
  2016-06-29 10:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 18:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9abdce70ac7a3ee8f92285c314fa7728d3c1aa43 ***

Author: Walter Lee <walt@tilera.com>
Branch: master
Commit: 9abdce70ac7a3ee8f92285c314fa7728d3c1aa43

[TILEPro] Don't build gdb

In configure.ac, add gdb to noconfigdirs for TILEPro.

       * configure.ac (tilepro-*-*): Add gdb to noconfigdirs.
       * configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Preserve all mapping symbols in ARM and AArch64 object files.
@ 2016-06-29 10:35 sergiodj+buildbot
  2016-06-29 11:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 10:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d691934d08a4132506a19ac8d7565f1a0461a80a ***

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

Preserve all mapping symbols in ARM and AArch64 object files.

bfd	* elfnn-aarch64.c (is_aarch64_mapping_symbol): New function.
	Returns TRUE for AArch64 mapping symbols.
	(elfNN_aarch64_backend_symbol_processing): New function.  Marks
	mapping symbols as precious in object files so that they will not
	be stripped.
	(elf_backend_symbol_processing): Define.

	* elf32-arm.c (is_arm_mapping_symbol): New function.  Returns TRUE
	for ARM mapping symbols.
	(elf32_arm_backend_symbol_processing): Make use of the new function.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use strtok_r instead of strsep in rust_get_disr_info
@ 2016-06-29 11:32 sergiodj+buildbot
  2016-06-29 13:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 11:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a405c2281ad29b5c7f9f2a4d58b7cfef2b74ba99 ***

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

Use strtok_r instead of strsep in rust_get_disr_info

strsep doesn't exist on Windows.

2016-06-29  Manish Goregaokar  <manish@mozilla.com>

gdb/ChangeLog:
    * rust-lang.c (rust_get_disr_info): Use strtok_r instead of strsep.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sparc: make SPARC_OPCODE_ARCH_MAX part of its enum
@ 2016-06-29 12:11 sergiodj+buildbot
  2016-06-29 14:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 12:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 042c94de565ae62640c064f1cb33d28484aeb9d3 ***

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

sparc: make SPARC_OPCODE_ARCH_MAX part of its enum

include/ChangeLog:

2016-06-29  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* opcode/sparc.h (enum sparc_opcode_arch_val): Move
	SPARC_OPCODE_ARCH_MAX into the enum.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Set unknown_syscall differently on arm linux
@ 2016-06-29 14:20 sergiodj+buildbot
  2016-06-29 16:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 14:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28244707d9e4f35cab1f9069cee1d44b38be095f ***

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

Set unknown_syscall differently on arm linux

Currently, we use 123456789 as unknown or illegal syscall number, and
expect program return ENOSYS.  Although 123456789 is an illegal syscall
number on arm linux, kernel sends SIGILL rather than returns -ENOSYS.
However, arm linux kernel returns -ENOSYS if syscall number is within
0xf0001..0xf07ff, so we can use 0xf07ff for unknown_syscall in test.

gdb/testsuite:

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

	* gdb.base/catch-syscall.c [__arm__]: Set unknown_syscall to
	0x0f07ff.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Initialize strtok_r's saveptr to NULL
@ 2016-06-29 14:59 sergiodj+buildbot
  2016-06-29 17:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9bf74fb27dc6e2a9679403d66fe919215e3c2a45 ***

Author: Manish Goregaokar <manish@mozilla.com>
Branch: master
Commit: 9bf74fb27dc6e2a9679403d66fe919215e3c2a45

Initialize strtok_r's saveptr to NULL

Building gdb with --enable-build-with-cxx=no trips on a warning:

 ../../binutils-gdb/gdb/rust-lang.c:173:15: error: saveptr may be used
 uninitialized in this function [-Werror=maybe-uninitialized]
     ret.name = concat (TYPE_NAME (type), "::", token, (char *) NULL);

The problem is that gcc doesn't understand that "tail" can never be
NULL in the call to strtok_r:

      name = xstrdup (TYPE_FIELD_NAME (type, 0));
      cleanup = make_cleanup (xfree, name);
      tail = name + strlen (RUST_ENUM_PREFIX);
...
      for (token = strtok_r (tail, "$", &saveptr);

Fix this by always initializing saveptr.

2016-06-29  Manish Goregaokar  <manish@mozilla.com>

gdb/ChangeLog:
    * rust-lang.c (rust_get_disr_info): Initialize saveptr to NULL.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR gdb/17210 - fix possible memory leak in read_memory_robust
@ 2016-06-29 16:36 sergiodj+buildbot
  2016-06-29 18:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 16:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d78f827e0da9ab6fda2d6ef2d59cebb805b411f ***

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

PR gdb/17210 - fix possible memory leak in read_memory_robust

PR gdb/17210 concerns a possible memory leak in read_memory_robust.
The bug can happen because read_memory_robust allocates memory, does
not install any cleanups, and invokes QUIT.  Similarly, target_read
calls QUIT, so it too can potentially throw.

The fix is to install cleanups to guard the allocated memory.

Built and regtested on x86-64 Fedora 23.  I couldn't think of a way to
test this, so no new test; and of course this means it should have
more careful review.

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

	PR gdb/17210:
	* target.c (free_memory_read_result_vector): Take a pointer to the
	VEC as an argument.
	(read_memory_robust): Install a cleanup for "result".
	* mi/mi-main.c (mi_cmd_data_read_memory_bytes): Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR python/20129 - use of non-existing variable
@ 2016-06-29 16:58 sergiodj+buildbot
  2016-06-29 20:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 16:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 803b47e5d4dc86b953aba0bc44865de287726dbe ***

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

Fix PR python/20129 - use of non-existing variable

PR python/20129 concerns the error message one gets from a command
like "disable frame-filter global NoSuchFilter".  Currently this
throws a second, unexpected, exception due to the use of a
non-existing variable named "name".

This patch adds regression tests and fixes a couple of spots to use
the correct variable name.

Built and regtested on x86-64 Fedora 23.

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

	PR python/20129:
	* python/lib/gdb/command/frame_filters.py (_do_enable_frame_filter)
	(SetFrameFilterPriority._set_filter_priority): Use "frame_filter",
	not "name".

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

	PR python/20129:
	* gdb.python/py-framefilter.exp: Add tests for setting priority
	and disabling of non-existent frame filter.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add copyright header in gdb.base/return.c
@ 2016-06-29 18:30 sergiodj+buildbot
  2016-06-29 21:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 18:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e56534680d0df0e2ca313086b1758480c9374615 ***

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

Add copyright header in gdb.base/return.c

gdb/testsuite:

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

	* gdb.base/return.c: Add copyright header.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for simulating big-endian AArch64 binaries.
@ 2016-06-30  8:28 sergiodj+buildbot
  2016-06-30 10:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-30  8:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c7be441465094e5ffce2f4205ea887676965d0be ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: c7be441465094e5ffce2f4205ea887676965d0be

Add support for simulating big-endian AArch64 binaries.

	* cpustate.h: Include config.h.
	(union GRegisterValue): Add WORDS_BIGENDIAN check.  For big endian code
	use anonymous structs to align members.
	* simulator.c (aarch64_step): Use sim_core_read_buffer and
	endian_le2h_4 to read instruction from pc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM][GAS] ARMv8.2 should enable ARMv8.1 NEON instructions.
@ 2016-06-30 10:07 sergiodj+buildbot
  2016-06-30 11:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-30 10:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 534dbe460e692a9befd9aca0eb0812db47459a30 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 534dbe460e692a9befd9aca0eb0812db47459a30

[ARM][GAS] ARMv8.2 should enable ARMv8.1 NEON instructions.

GAS fails to recognize march=armv8.2-a as a superset of march=armv8.1-a
when assembling NEON instructions. The patch corrects this, making
-march=armv8.2-a -mfpu=neon-fp-armv8 enable the NEON intructions
introduced with ARMv8.1-A.

include/
2016-06-30  Matthew Wahab  <matthew.wahab@arm.com>

	* opcode/arm.h (ARM_ARCH_V8_2a): Add FPU_NEON_EXT_RDMA to the set
	of enabled FPU features.

gas/
2016-06-30  Matthew Wahab  <matthew.wahab@arm.com>

	* testsuite/gas/arm/armv8_2+rdma.d: New.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Make testing gdb with FORCE_SEPARATE_MI_TTY=1 actually work
@ 2016-06-30 11:28 sergiodj+buildbot
  2016-06-30 12:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-30 11:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 994e9c834d916af85e0fe0e8c3e18259aa4be389 ***

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

Make testing gdb with FORCE_SEPARATE_MI_TTY=1 actually work

Runing the whole gdb testsuite with MI on a separate tty, with:

  make check RUNTESTFLAGS="FORCE_SEPARATE_MI_TTY=1"

Doesn't actually work because commit 51f77c3704a6 ("Add testing
infrastruture bits for running with MI on a separate UI") included a
last-minute rename typo, now fixed with this commit.

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

	* lib/mi-support.exp (default_mi_gdb_start): Declare global
	FORCE_SEPARATE_MI_TTY, not SEPARATE_MI_TTY.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdbserver/MI testing regression
@ 2016-06-30 11:43 sergiodj+buildbot
  2016-06-30 15:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-06-30 11:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 038d48680941f014349256aeb7bab14b3f01d58e ***

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

Fix gdbserver/MI testing regression

Commit 51f77c3704a6 ("Add testing infrastruture bits for running with
MI on a separate UI") broke MI testing with native-gdbserver:

 $ make check RUNTESTFLAGS="--target_board=native-gdbserver mi-var-child.exp"
	 ...
 Running .../src/binutils-gdb/gdb/testsuite/gdb.mi/mi-var-child.exp ...
 can't unset "inferior_spawn_id": no such variable
     while executing
 "unset inferior_spawn_id"
     (procedure "close_gdbserver" line 20)
     invoked from within
 "close_gdbserver"
 ...

When testing with gdbserver, gdb_exit is overridden with a special
version that calls close_gdbserver, which clears inferior_spawn_id.
The problem is that the commit mentioned above made
gdb_exit/mi_gdb_exit clear inferior_spawn_id too, and clearing a
non-existing variable is a tcl error.

Since gdb_exit/mi_gdb_exit always clears inferior_spawn_id now, the
fix is simply to stop clearing it in close_gdbserver.

gdb/testsuite/
2016-06-30  Pedro Alves  <palves@redhat.com>

	* lib/gdbserver-support.exp (close_gdbserver, gdb_exit): Don't
	unset inferior_spawn_id.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86/Intel: fix operand checking for MOVSD
@ 2016-07-01  7:09 sergiodj+buildbot
  2016-07-01  8:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01  7:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8325cc6398187c12e0fe04a68a21e4eb5f44fa20 ***

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

x86/Intel: fix operand checking for MOVSD

The dual purpose mnemonic (string move vs scalar double move) breaks
the assumption that the isstring flag would be set on both the first
and last entry in the current set of templates, which results in bogus
or missing diagnostics for the string move variant of the mnemonic.
Short of mostly rewriting i386_index_check() and its interaction with
the rest of the code, simply shrink the template set to just string
instructions when encountering the second memory operand, and run
i386_index_check() a second time for the first memory operand after
that reduction.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: remove stray instruction attributes
@ 2016-07-01  7:49 sergiodj+buildbot
  2016-07-01  9:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01  7:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9243100aef7486524f1a7f87bbd2cce1fe980b75 ***

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

x86: remove stray instruction attributes

- with Cpu64 Disp16 makes no sense for memory operands
- with CpuNo64 Disp32S makes no sense
- non-64-bit lgdt doesn't allow 10-byte operands


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: allow suffix-less movzw and 64-bit movzb
@ 2016-07-01  8:42 sergiodj+buildbot
  2016-07-01 10:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01  8:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c07315e0c610e0e3317b4c02266f81793df253d2 ***

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

x86: allow suffix-less movzw and 64-bit movzb

... just like is already the case for 16- and 32-bit movzb: I can't see
why omitting suffixes on this (and movs{b,w,l}) is not allowed, when it
is allowed for all other instructions where the suffix is redundant
with (one of) the operands.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Factor out "Detaching from program" message printing
@ 2016-07-01 10:53 sergiodj+buildbot
  2016-07-01 12:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 10:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f48b757071509040d800ff9f7c8726e5828bd1a ***

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

Factor out "Detaching from program" message printing

Several targets have a copy of the same code that prints

 "Detaching from program ..."

in their target_detach implementation.  Factor that out to a common
function.

(For now, I left the couple targets that print this a bit differently
alone.  Maybe this could be further pulled out into infcmd.c.  If we
did that, and those targets want to continue printing differently,
this new function could be converted to a target method.)

gdb/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>

	* darwin-nat.c (darwin_detach): Use target_announce_detach.
	* inf-ptrace.c (inf_ptrace_detach): Likewise.
	* nto-procfs.c (procfs_detach): Likewise.
	* remote.c (remote_detach_1): Likewise.
	* target.c (target_announce_detach): New function.
	* target.h (target_announce_detach): New declaration.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Forget watchpoint locations when inferior exits or is killed/detached
@ 2016-07-01 11:56 sergiodj+buildbot
  2016-07-01 13:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 11:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 630008884535a5b26828325e48e729034c110536 ***

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

Forget watchpoint locations when inferior exits or is killed/detached

If you have two inferiors (or more), set watchpoints in one of the
inferiors, and then that inferior exits, until you manually delete the
watchpoint (or something forces a breakpoint re-set), you can't resume
the other inferior.

This is exercised by the test added by this commit.  Without the GDB
fix, this test fails like this:

 FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=kill: continue to marker in inferior 1
 FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=detach: continue to marker in inferior 1
 FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=exit: continue to marker in inferior 1

and gdb.log shows (in all three cases):

 (gdb) continue
 Continuing.
 Warning:
 Could not insert hardware watchpoint 2.
 Could not insert hardware breakpoints:
 You may have requested too many hardware breakpoints/watchpoints.

 Command aborted.
 (gdb) FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=kill: continue to marker in inferior 1

The problem is that GDB doesn't forget about the locations of
watchpoints set in the inferior that is now dead.  When we try to
continue the inferior that is still alive, we reach
insert_breakpoint_locations, which has the the loop that triggers the
error:

  /* If we failed to insert all locations of a watchpoint, remove
     them, as half-inserted watchpoint is of limited use.  */

That loop finds locations that are not marked inserted, but which
according to should_be_inserted should have been inserted, and so
errors out.

gdb/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (breakpoint_init_inferior): Discard watchpoint
	locations.
	* infcmd.c (detach_command): Call breakpoint_init_inferior.

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

	* gdb.multi/watchpoint-multi-exit.c: New file.
	* gdb.multi/watchpoint-multi-exit.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix failure to detach if process exits while detaching on Linux
@ 2016-07-01 12:41 sergiodj+buildbot
  2016-07-01 14:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 12:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ced2dffbf17bc661e959da1e39411d706ade9f77 ***

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

Fix failure to detach if process exits while detaching on Linux

This commit fixes detaching on Linux when some thread exits the whole
thread group (process) just while we're detaching.

On Linux, a ptracer must detach from each LWP individually, with
PTRACE_DETACH.  Since PTRACE_DETACH sets the thread running free, if
one of the already-detached threads causes the whole thread group to
exit (e.g., simply calls exit), the kernel force-kills the other
threads in the group, making them zombie, just as we're still
detaching them.  Since PTRACE_DETACH against a zombie thread fails
with ESRCH, and gdb/gdbserver are not expecting this, the detach fails
with an error like: "Can't detach process: No such process.".

This patch detects this detach failure as normal, and instead of
erroring out, reaps the now-dead thread.

New test included, that exercises several different scenarios that
cause GDB/GDBserver to error out when it should not.

Tested on x86-64 GNU/Linux with {unix, native-gdbserver,
native-extended-gdbserver}

Note: without the previous fix, the "single-process + continue"
variant of the new test would fail with:

 (gdb) PASS: gdb.threads/process-dies-while-detaching.exp: single-process: continue: watchpoint: switch to parent
 continue
 Continuing.
 Warning:
 Could not insert hardware watchpoint 3.
 Could not insert hardware breakpoints:
 You may have requested too many hardware breakpoints/watchpoints.

 Command aborted.
 (gdb) FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: continue: watchpoint: continue

gdb/gdbserver/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>
	    Antoine Tremblay  <antoine.tremblay@ericsson.com>

	* linux-low.c: Change interface to take the target lwp_info
	pointer directly and return void.  Handle detaching from a zombie
	thread.
	(linux_detach_lwp_callback): New function.
	(linux_detach): Detach from the leader thread after detaching from
	the clone threads.

gdb/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>
	    Antoine Tremblay  <antoine.tremblay@ericsson.com>

	* inf-ptrace.c (inf_ptrace_detach_success): New function, factored
	out from ...
	(inf_ptrace_detach): ... here.
	* inf-ptrace.h (inf_ptrace_detach_success): New declaration.
	* linux-nat.c (get_pending_status): Rename to ...
	(get_detach_signal): ... this, and return a host signal instead of
	filling in a wait status.
	(detach_one_lwp): New function, factored out from detach_callback
	and adjusted to handle detaching from a zombie thread.
	(detach_callback): Skip the leader thread.
	(linux_nat_detach): No longer defer to inf_ptrace_detach to detach
	the leader thread, nor build a signal string to pass down.
	Instead, use target_announce_detach, detach_one_lwp and
	inf_ptrace_detach_success.

gdb/testsuite/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>
	    Antoine Tremblay  <antoine.tremblay@ericsson.com>

	* gdb.threads/process-dies-while-detaching.c: New file.
	* gdb.threads/process-dies-while-detaching.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Extend JIT-reader test and fix GDB problems that exposes
@ 2016-07-01 12:59 sergiodj+buildbot
  2016-07-01 16:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 12:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20aa2c606ef682889722b03b1d874befa84fbf53 ***

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

Extend JIT-reader test and fix GDB problems that exposes

The jit-reader.exp test isn't really exercising the jit-reader's
unwinder API at all.  This commit address that, and then fixes GDB
problems exposed.

- The custom JIT reader provided for the jit-reader.exp testcase
  always rejects the jitted function's frame...

  This is because the custom JIT reader in the testcase never ever
  sets state->code_begin/end, so the bounds check in
  gdb.base/jitreader.c:unwind_frame:

   if (this_ip >= state->code_end || this_ip < state->code_begin)
     return GDB_FAIL;

  tends to fail, unless you're "lucky" (because it references
  uninitialized data).

  The result is that GDB is always actually using a built-in unwinder
  for the jitted function.

- The provided unwinder doesn't do anything that GDB's built-in
  unwinder can't do.

  IOW, we can't really tell whether the JIT reader's unwinder is
  working or not.

  I fixed that by making the jitted function mangle its own stack
  pointer with a xor, and then teaching the jit unwinder to demangle
  it back (another xor).  So now "backtrace" with GDB's built-in
  unwinder fails while with the jit unwinder, it succeeds.

- GDB crashes after unloading the JIT reader, and flushing frames...

  I made the testcase use the "flushregs" command after unloading the
  JIT reader, to force the JIT frames to be flushed.  However, that
  crashes GDB...

  When reinit_frame_cache tears down a frame's cache, it calls its
  unwinder's dealloc_cache method, which for JIT frames ends up in
  jit.c:jit_dealloc_cache.  This function calls each of the frame's
  gdb_reg_value's "free" pointer:

   for (i = 0; i < gdbarch_num_regs (frame_arch); i++)
     if (priv_data->registers[i] && priv_data->registers[i]->free)
       priv_data->registers[i]->free (priv_data->registers[i]);

  and the problem is these gdb_reg_value instances have been returned
  by the JIT reader that has been already unloaded, and their "free"
  function pointers likely point to functions in the DSO that has
  already been unloaded...

  A fix for that could be to call reinit_frame_cache in
  jit_reader_unload_command _before_ unloading the jit reader DSO so
  that the jit reader is given a chance to clean up the gdb_reg_values
  before it is unloaded.  However, the fix for the point below makes
  this unnecessary, because it stops jit.c from keeping around
  gdb_reg_values in the first place.

- However, it still makes sense to clear the frame cache when loading
  or unloading a JIT unwinder.

  This makes testing a JIT unwinder a bit simpler.

- Not only the frame cache actually -- gdb is not unloading the
  jit-registered objfiles when the JIT reader is unloaded, and not
  loading the already-registered descriptors when a JIT reader is
  loaded.

  The new test exercises unloading the jit reader, loading it back
  again, and then making sure the JIT reader's unwinder works again.
  Without the unload/re-load of already-read descriptors, the newly
  loaded JIT would have no idea where the new function is, because
  it's stored at symbol read time.

- I added a couple "info frame" calls to the test, and that
  crashes GDB...

  The problem is that jit_frame_prev_register assumes it'll only be
  called for raw registers, so when it gets a pseudo register number,
  the "priv->registers[reg]" access is really an out-of-bounds access.

  To fix that, I made jit_frame_prev_register use
  gdbarch_pseudo_register_read_value for reading the pseudo-registers.
  However, that works with a regcache and we don't have one.  To fix
  that, I made the JIT unwinder store a regcache in its cache instead
  of an array of gdb_reg_value pointers.

gdb/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>
	    Tom Tromey  <tom@tromey.com>

	* jit.c (jit_reader_load_command): Call reinit_frame_cache and
	jit_inferior_created_hook.
	(jit_reader_unload_command): Call reinit_frame_cache and
	jit_inferior_exit_hook.
	* jit.c (struct jit_unwind_private) <registers>: Delete field.
	<regcache>: New field.
	(jit_unwind_reg_set_impl): Set the register's value in the
	regcache.  Free the passed-in gdb_reg_value.
	(jit_dealloc_cache): Adjust to free the regcache.
	(jit_frame_sniffer): Allocate a regcache instead of an array of
	gdb_reg_value pointers.
	(jit_frame_this_id): Adjust.
	(jit_frame_prev_register): Read raw registers off of the regcache
	instead of from the gdb_reg_value pointer array.  Use
	gdbarch_pseudo_register_read_value to read pseudo registers.
	* regcache.c (regcache_raw_set_cached_value): New function,
	factored out from ...
	(regcache_raw_write): ... here.
	* regcache.h (regcache_raw_set_cached_value): Declare.

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

	* gdb.base/jit-reader.exp (info_registers_current_frame): New
	procedure.
	(jit_reader_test): Test the jit reader's unwinder.
	* gdb.base/jithost.c (jit_function_00_code): New global.
	(main): Use memcpy to fill in the mmapped code, instead of poking
	bytes manually here.
	* gdb.base/jitreader.c (enum register_mapping) <AMD64_RBP>: New
	value.
	(read_debug_info): Save the function's range.
	(read_sp): New function.
	(unwind_frame): Use it.  Also unwind RBP.
	(get_frame_id): Use read_sp.
	(gdb_init_reader): Use calloc instead of malloc.
	* lib/gdb.exp (get_hexadecimal_valueof): Add optional 'test'
	parameter.  Use gdb_test_multiple.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Consolidate x86 debug register code for BSD native targets.
@ 2016-07-01 14:59 sergiodj+buildbot
  2016-07-01 17:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a3405d124e1388b613a35af49f19f0cc1b8d959d ***

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

Consolidate x86 debug register code for BSD native targets.

Move the debug register support code from amd64bsd-nat.c and
i386bsd-nat.c into a shared x86bsd-nat.c.

Instead of setting up x86_dr_low in amd64fbsd-nat.c and
i386fbsd-nat.c, add a x86bsd_target function that creates a new target
that inherits from inf_ptrace and sets up x86 debug registers if
supported.  In addition to initializing x86_dr_low, the x86bsd target
installs a custom mourn_inferior target operation to clean up the
x86 debug register state.  Previously this was only done on amd64.
Now it will be done for both i386 and amd64.  The i386bsd_target and
amd64bsd_target functions create targets that inherit from x86bsd
rather than inf_ptrace.

gdb/ChangeLog:

	* Makefile.in [HFILES_NO_SRCDIR]: Replace 'amd64bsd-nat.h' with
	'x86bsd-nat.h'.
	* amd64bsd-nat.c: Include 'x86bsd-nat.h' instead of
	'amd64bsd-nat.h'.
	(amd64bsd_xsave_len): Rename and move to x86bsd-nat.c.
	(amd64bsd_fetch_inferior_registers): Replace 'amd64bsd_xsave_len'
	with 'x86bsd_xsave_len'.
	(amd64bsd_store_inferior_registers): Likewise.
	(amd64bsd_target): Inherit from x86bsd_target.
	(amd64bsd_dr_get): Rename and move to x86bsd-nat.c.
	(amd64bsd_dr_set): Likewise.
	(amd64bsd_dr_set_control): Likewise.
	(amd64bsd_dr_set_addr): Likewise.
	(amd64bsd_dr_get_addr): Likewise.
	(amd64bsd_dr_get_status): Likewise.
	(amd64bsd_dr_get_control): Likewise.
	* amd64fbsd-nat.c: Include 'x86bsd-nat.h' instead of
	'amd64bsd-nat.h'.
	(super_mourn_inferior): Move to x86bsd-nat.c.
	(amd64fbsd_mourn_inferior): Rename and move to x86bsd-nat.c.
	(amd64fbsd_read_description): Replace 'amd64bsd_xsave_len' with
	'x86bsd_xsave_len'.
	(_initialize_amd64fbsd_nat): Remove x86 watchpoint setup and
	mourn_inferior' target op.
	* config/i386/fbsd.mh (NATDEPFILES): Add x86bsd-nat.o.
	* config/i386/fbsd64.mh: Likewise.
	* config/i386/nbsd64.mh: Likewise.
	* config/i386/nbsdelf.mh: Likewise.
	* config/i386/obsd.mh: Likewise.
	* config/i386/obsd64.mh: Likewise.
	* i386bsd-nat.c: Include 'x86bsd-nat.h'.
	(i386bsd_xsave_len): Rename and move to x86bsd-nat.c.
	(i386bsd_fetch_inferior_registers): Replace 'i386bsd_xsave_len'
	with 'x86bsd_xsave_len'.
	(i386bsd_store_inferior_registers): Likewise.
	(i386bsd_target): Inherit from x86bsd_target.
	(i386bsd_dr_get): Rename and move to x86bsd-nat.c.
	(i386bsd_dr_set): Likewise.
	(i386bsd_dr_set_control): Likewise.
	(i386bsd_dr_set_addr): Likewise.
	(i386bsd_dr_get_addr): Likewise.
	(i386bsd_dr_get_status): Likewise.
	(i386bsd_dr_get_control): Likewise.
	* i386bsd-nat.h (i386bsd_xsave_len): Remove.
	(i386bsd_dr_set_control): Remove.
	(i386bsd_dr_set_addr): Remove.
	(i386bsd_dr_get_addr): Remove.
	(i386bsd_dr_get_status): Remove.
	(i386bsd_dr_get_control): Remove.
	* i386fbsd-nat.c: Include 'x86bsd-nat.h'.
	(i386fbsd_read_description): Replace 'i386bsd_xsave_len' with
	'x86bsd_xsave_len'.
	(_initialize_i386fbsd_nat): Remove x86 watchpoint setup and
	mourn_inferior' target op.
	* x86bsd-nat.c: New file.
	* x86bsd-nat.h: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Set debug registers on all threads belonging to the current inferior.
@ 2016-07-01 15:50 sergiodj+buildbot
  2016-07-01 18:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5077bfff905136e9d9a8fdf0886f6217887622ad ***

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

Set debug registers on all threads belonging to the current inferior.

gdb/ChangeLog:

	* x86bsd-nat.c: Include 'gdbthread.h'.
	(x86bsd_dr_set): Set debug registers on all threads belonging to
	the current inferior.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix Thumb-2 BL detection
@ 2016-07-01 16:41 sergiodj+buildbot
  2016-07-01 20:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e866f5aeeaf7514f5ca4f9eaba41594eac22e5b ***

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

Fix Thumb-2 BL detection

2016-07-01  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (using_thumb2_bl): New function.
	(arm_type_of_stub): Declare thumb2 variable together and change type
	to bfd_boolean.  Use using_thumb2_bl () to determine whether
	THM_MAX_FWD_BRANCH_OFFSET or THM2_MAX_FWD_BRANCH_OFFSET should be
	checked for BL range.
	(elf32_arm_final_link_relocate): Use using_thumb2_bl () to determine
	the bit size of BL offset.

ld/
	* testsuite/ld-arm/arm-elf.exp (Thumb-2 BL): Assemble for ARMv7.
	(Thumb-2 BL on ARMv6-M): New testcase.
	* testsuite/ld-arm/thumb2-bl.d: Do not try to match testcase filename.
	* testsuite/ld-arm/thumb2-bl.s: Do not select architecture.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Honor detach-on-fork on FreeBSD.
@ 2016-07-01 17:17 sergiodj+buildbot
  2016-07-01 21:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb2a62e694953c099c41d49f59947d3d91cc7c27 ***

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

Honor detach-on-fork on FreeBSD.

Only detach from the new child process in the follow fork callback
if detach_fork is true.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_follow_fork): Only detach child if
	"detach_fork" is true.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Move fbsd_resume and related functions below fork following helper code.
@ 2016-07-01 18:19 sergiodj+buildbot
  2016-07-01 22:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8607ea632c806235554aa2336cf01bf3758c1264 ***

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

Move fbsd_resume and related functions below fork following helper code.

gdb/ChangeLog:

	* fbsd-nat.c (super_resume): Move earlier next to "super_wait".
	(resume_one_thread_cb): Move below fork following helper code.
	(resume_all_threads_cb): Likewise.
	(fbsd_resume): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fake VFORK_DONE events when following only the parent after a vfork.
@ 2016-07-01 18:48 sergiodj+buildbot
  2016-07-02  0:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 18:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c5c2a3321706c28cbf1b85a970a2e32912eb0c8 ***

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

Fake VFORK_DONE events when following only the parent after a vfork.

FreeBSD does not currently report a ptrace event for a parent process
after it resumes due to the child exiting the shared memory region after
a vfork.  Take the same approach used in linux-nat.c in this case of
sleeping for a while and then reporting a fake VFORK_DONE event.

gdb/ChangeLog:

	* fbsd-nat.c (struct fbsd_fork_child_info): Rename to ...
	(struct fbsd_fork_info): ... this.
	(struct fbsd_fork_info) <child>: Rename to ...
	(struct fbsd_fork_info) <ptid>: ... this.
	(fbsd_pending_children): Update type.
	(fbsd_remember_child): Update type and field name.
	(fbsd_is_child_pending): Likewise.
	(fbsd_pending_vfork_done): New variable.
	(fbsd_is_vfork_done_pending): New function.
	(fbsd_next_vfork_done): New function.
	(fbsd_resume): Don't resume processes with a pending vfork done
	event.
	(fbsd_wait): Report pending vfork done events.
	(fbsd_follow_fork): Delay and record a pending vfork done event
	for a vfork parent when detaching the child.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Fix +nofp16 handling
@ 2016-07-01 19:44 sergiodj+buildbot
  2016-07-02  1:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 19:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93d8990cba700abdf9d2be06a5022e588d097fc8 ***

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

[AArch64] Fix +nofp16 handling

Feature flag handling was not perfect, +nofp16 disabled fp
instructions too.

New feature flag macros were added to check features with multiple
bits set (matters for FP_F16 and SIMD_F16 opcode feature tests).
The unused AARCH64_OPCODE_HAS_FEATURE was removed, all checks should
use one of the AARCH64_CPU_HAS_* macros.  AARCH64_CPU_HAS_FEATURE
now checks all feature bits.

The aarch64_features table now contains the dependencies as
a separate field (so when the feature is enabled all dependencies
are enabled and when it is disabled everything that depends on it
is disabled).

Note that armv8-a+foo+nofoo is not equivalent to armv8-a if
+foo turns on dependent features that nofoo does not turn off.

gas/
	* config/tc-aarch64.c (struct aarch64_option_cpu_value_table): Add
	require field.
	(aarch64_features): Initialize require fields.
	(aarch64_parse_features): Handle dependencies.
	(aarch64_feature_enable_set, aarch64_feature_disable_set): New.
	(md_assemble): Use AARCH64_CPU_HAS_ALL_FEATURES.
	* testsuite/gas/aarch64/illegal-nofp16.s: New.
	* testsuite/gas/aarch64/illegal-nofp16.l: New.
	* testsuite/gas/aarch64/illegal-nofp16.d: New.

include/
	* opcode/aarch64.h (AARCH64_CPU_HAS_ALL_FEATURES): New.
	(AARCH64_CPU_HAS_ANY_FEATURES): New.
	(AARCH64_CPU_HAS_FEATURE): Define as AARCH64_CPU_HAS_ALL_FEATURES.
	(AARCH64_OPCODE_HAS_FEATURE): Remove.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Optimize memory_xfer_partial for remote
@ 2016-07-01 19:49 sergiodj+buildbot
  2016-07-02  2:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 19:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09c98b448f3d89cb9576e4e73991c2312939e0af ***

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

Optimize memory_xfer_partial for remote

Some analysis we did here showed that increasing the cap on the
transfer size in target.c:memory_xfer_partial could give 20% or more
improvement in remote load across JTAG.  Transfer sizes were capped
to 4K bytes because of performance problems encountered with the
restore command, documented here:

https://sourceware.org/ml/gdb-patches/2013-07/msg00611.html

and in commit 67c059c29e1f ("Improve performance of large restore
commands").

The 4K cap was introduced because in a case where the restore command
requested a 100MB transfer, memory_xfer_partial would repeatedy
allocate and copy an entire 100MB buffer in order to properly handle
breakpoint shadow instructions, even though memory_xfer_partial would
actually only write a small portion of the buffer contents.

A couple of alternative solutions were suggested:
* change the algorithm for handling the breakpoint shadow instructions
* throttle the transfer size up or down based on the previous actual
  transfer size

I tried implementing the throttling approach, and my implementation
reduced the performance in some cases.

This patch implements a new target function that returns that target's
limit on memory transfer size.  It defaults to ULONGEST_MAX bytes,
because for native targets there is no marshaling and thus no limit is
needed.  For remote targets it uses get_memory_write_packet_size.

gdb/ChangeLog:

	* remote.c (remote_get_memory_xfer_limit): New function.
	* target-delegates.c: Regenerate.
	* target.c (memory_xfer_partial): Call
	target_ops.to_get_memory_xfer_limit.
	* target.h (struct target_ops)
	<to_get_memory_xfer_limit>: New member.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] babeltrace compilation regression
@ 2016-07-05  9:02 sergiodj+buildbot
  2016-07-05 10:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-05  9:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13cdc2afb7873547ec2910ba647fb4a68602252f ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 13cdc2afb7873547ec2910ba647fb4a68602252f

babeltrace compilation regression

Since:
	commit 2d681be471cf8aff8f296cb7713c39e9aa4fc2bb
	Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
	Date:   Wed Apr 27 15:52:16 2016 +0200
	    Avoid non-C++-enabled babeltrace versions
tested with:
	libbabeltrace-devel-1.2.4-4.fc24.x86_64
	libbabeltrace-devel-1.4.0-2.fc25.x86_64
it can no longer build due to:
	configure:16435: gcc -o conftest -m64 -g3 -pipe -Wall -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -fno-diagno
stics-show-caret  -Werror  -static-libstdc++ -static-libgcc  conftest.c -ldl -ldl -lncurses -lm -ldl  -lbabeltrace -lbabeltrace-ctf >&5
	conftest.c: In function 'main':
	conftest.c:208:7: error: 'pos' is a pointer; did you mean to use '->'?

gdb/ChangeLog
2016-07-05  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* configure: Regenerate.
	* configure.ac (HAVE_LIBBABELTRACE): Fix pos variable dereference.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] Change noread to purecode.
@ 2016-07-05 10:56 sergiodj+buildbot
  2016-07-05 12:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-05 10:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0728ee368f217f2473798ad7ccfe9feae4412ce ***

Author: Andre Vieria <andre.simoesdiasvieira@arm.com>
Branch: master
Commit: f0728ee368f217f2473798ad7ccfe9feae4412ce

[ARM] Change noread to purecode.

bfd/ChangeLog
2016-07-05  Andre Vieria  <andre.simoesdiasvieira@arm.com>

        * bfd-in2.h (SEC_ELF_NOREAD): Rename to ...
          (SEC_ELF_PURECODE): ... this.
        * elf32-arm.c (elf32_arm_post_process_headers): Rename SEC_ELF_NOREAD
          to SEC_ELF_NOREAD.
          (elf32_arm_fake_sections): Likewise.
          (elf_32_arm_section_flags): Likewise.
          (elf_32_arm_lookup_section_flags): Likewise.
        * section.c (SEC_ELF_NOREAD): Rename to ...
          (SEC_ELF_PURECODE): ... this.

binutils/ChangeLog
2016-07-05  Andre Vieria  <andre.simoesdiasvieira@arm.com>

        * objdump.c (dump_section_header): Rename SEC_ELF_NOREAD
          to SEC_ELF_NOREAD.
        * readelf.c (get_elf_section_flags): Rename ARM_NOREAD to
          ARM_PURECODE and SHF_ARM_NOREAD to SHF_ARM_PURECODE.
          (process_section_headers): Rename noread to purecode.

        * section.c (SEC_ELF_NOREAD): Rename to ...
          (SEC_ELF_PURECODE): ... this.

include/ChangeLog
2016-07-05  Andre Vieria  <andre.simoesdiasvieira@arm.com>

        * elf/arm.h (SHF_ARM_NOREAD): Rename to ...
          (SHF_ARM_PURECODE): ... this.

ld/ChangeLog
2016-07-05  Andre Vieria  <andre.simoesdiasvieira@arm.com>

        * testsuite/ld-arm/arm_noread.ld: Renamed to ...
          testsuite/ld-arm/arm_purecode.ld: ... this, and replaced
          all noread's by purecode.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] Purecode compatible long branch veneer for M-profile targets with MOVW.
@ 2016-07-05 11:42 sergiodj+buildbot
  2016-07-05 13:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-05 11:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5a67c02901c0abe946546f2b3b1a3b67a876136 ***

Author: Andre Vieria <andre.simoesdiasvieira@arm.com>
Branch: master
Commit: d5a67c02901c0abe946546f2b3b1a3b67a876136

[ARM] Purecode compatible long branch veneer for M-profile targets with MOVW.

2016-07-05  Andre Vieria  <andre.simoesdiasvieira@arm.com>

	* elf32-arm.c (THUMB32_MOVT): New veneer macro.
	(THUMB32_MOVW): Likewise.
	(elf32_arm_stub_long_branch_thumb2_only_pure): New.
	(DEF_STUBS): Define long_branch_thumb2_only_pure.
	(arm_stub_is_thumb): Add new veneer stub.
	(arm_type_of_stub): Use new veneer.
	(arm_stub_required_alignment): Add new veneer.

2016-07-05  Andre Vieria  <andre.simoesdiasvieira@arm.com>

	* testsuite/ld-arm/farcall-thumb2-purecode.d: New test result.
	* testsuite/ld-arm/farcall-thumb2-purecode.s: New test.
	* testsuite/ld-arm/arm-elf.exp: Run it.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix fail in gdb.mi/mi-reverse.exp
@ 2016-07-05 14:06 sergiodj+buildbot
  2016-07-05 15:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-05 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 647c264cb2c60c90ee2d09edb6bd001ff357306d ***

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

Fix fail in gdb.mi/mi-reverse.exp

Commit 38b022b4452f996fb5a8598f80d850b594621bcf adds "method" and
"format" fields in =record-started, but doesn't update test case
gdb.mi/mi-reverse.exp, so it causes the fail like this,

PASS: gdb.mi/mi-reverse.exp: mi runto main
Expecting: ^(-interpreter-exec console record[^M
]+)?(=record-started,thread-group="i1"^M
\^done[^M
]+[(]gdb[)] ^M
[ ]*)
-interpreter-exec console record^M
=record-started,thread-group="i1",method="full"^M
^done^M
(gdb) ^M
FAIL: gdb.mi/mi-reverse.exp: Turn on process record

and regression was found by buildbot too
https://sourceware.org/ml/gdb-testers/2016-q2/msg04492.html

gdb/testsuite:

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

	* gdb.mi/mi-reverse.exp: Match =record-started output.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Allow subscripting raw pointers
@ 2016-07-06  5:38 sergiodj+buildbot
  2016-07-06  6:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-06  5:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 42d940118a6372d6e85f71a54fed75fdf5c606bd ***

Author: Manish Goregaokar <manish@mozilla.com>
Branch: master
Commit: 42d940118a6372d6e85f71a54fed75fdf5c606bd

Allow subscripting raw pointers

This will be useful for dealing with vectors; regardless of our final solution
for the Index trait.

2016-07-06  Manish Goregaokar  <manish@mozilla.com>

gdb/ChangeLog:
    * rust-lang.c (rust_subscript): Allow subscripting pointers

gdb/testsuite/ChangeLog:
    * simple.rs: Add test for raw pointer subscripting
    * simple.exp: Add test expectations


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] Fix endless recursion on calculating CPRC candidate
@ 2016-07-06  7:38 sergiodj+buildbot
  2016-07-06  8:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-06  7:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1040b979bc46474530fa4fee397b8acc460c01e9 ***

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

[ARM] Fix endless recursion on calculating CPRC candidate

When GDB determines whether type T can be part of candidate for
passing and returning in VFP registers, it calls
arm_vfp_cprc_sub_candidate recursively.  However, if type T has
self-reference field, like,

class C
{
  static C s;
};

arm_vfp_cprc_sub_candidate won't return.  This fix is to skip calling
arm_vfp_cprc_sub_candidate if the field is static.

gdb:

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

	* arm-tdep.c (arm_vfp_cprc_sub_candidate): Don't call
	arm_vfp_cprc_sub_candidate for static field.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use 'ptid_t' instead of 'ptid' for fbsd_next_vfork_done's return type.
@ 2016-07-06 13:14 sergiodj+buildbot
  2016-07-06 14:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 13:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee950322ca2c77494b1742f304632f667ed6ce79 ***

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

Use 'ptid_t' instead of 'ptid' for fbsd_next_vfork_done's return type.

'ptid' compiles in C++, but not C.

gdb/ChangeLog:
	* fbsd-nat.c (fbsd_is_vfork_done_pending): Fix return type.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove check for negative size.
@ 2016-07-06 13:45 sergiodj+buildbot
  2016-07-06 15:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 13:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d66ff635bec25bf940cc6d173a92f7796f18b310 ***

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

Remove check for negative size.

Since CORE_ADDR is unsigned, this value can never be negative.

gdb/ChangeLog:

	* score-tdep.c (score7_malloc_and_get_memblock): Remove check for
	negative size.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Set uses_fp for frames with a valid FP register explicitly.
@ 2016-07-06 14:25 sergiodj+buildbot
  2016-07-06 17:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 14:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ca107148e888a7f7aaf3582569708684bd04690 ***

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

Set uses_fp for frames with a valid FP register explicitly.

Since CORE_ADDR is unsigned, the saved FP register is always greater than
or equal to zero.  Replace the comparison by explicitly setting uses_fp to
1 for frames with a valid FP register.

gdb/ChangeLog:

	* sh64-tdep.c (sh64_analyze_prologue): Set "uses_fp" when setting
	the MEDIA_FP_REGNUM register.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use unsigned integer constant with left shifts.
@ 2016-07-06 15:28 sergiodj+buildbot
  2016-07-06 18:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 15:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db297a6501dc44c10bff096eddcc358b48810aad ***

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

Use unsigned integer constant with left shifts.

This avoids undefined behavior.

gdb/ChangeLog:

	* ada-lang.c (ada_unpack_from_contents): Use unsigned constants with
	left shifts.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove extraneous parentheses.
@ 2016-07-06 15:43 sergiodj+buildbot
  2016-07-19 16:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb36c6bf0a019e7b989e61710f17b5ce4ec27686 ***

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

Remove extraneous parentheses.

gdb/ChangeLog:

	* h8300-tdep.c (h8300_print_register): Remove extraneous parentheses.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix of default lookup for "this" symbol.
@ 2016-07-07 15:52 sergiodj+buildbot
  2016-07-20  2:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-07 15:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f19a0e6b45c63c0b4afe27a19d144cca412d4ae ***

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

Fix of default lookup for "this" symbol.

Using the default lookup for the symbol "this" might lead to segmentation
fault in GDB.
Some languages, e.g. Fortran, use as default lookup routine the C++
routines.
For those languages "this" can be the instance of a class or even the
definition of a class.
When an instance of a class having the name "this" is evaluated
in GDB a segmentation fault was observed.

As example of the issue take into consideration the Fortran code:
  type foo
    real :: a
    type(bar) :: x
    character*7 :: b
  end type foo
  type(foo) :: this

Issue appears when evaluating the variable "this" in GDB.

Within the language definition structure there is a field that represents
the name of the special symbol used for the C++ "this" for the language
being described.
The fix presented here takes into account the aforementioned field. In the
case the aforementioned field is NULL "this" is not represented in the
language described and the lookup should return a null_block_symbol.

Tests: Performed tests with gfortran and ifort.

Reviewed:
https://sourceware.org/ml/gdb-patches/2016-04/msg00068.html

After the commited patch:
https://sourceware.org/ml/gdb-patches/2016-06/msg00364.html
Patch can be applied.

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

gdb/ChangeLog:

	* cp-namespace.c (cp_lookup_bare_symbol): Use language passed as
	parameter to look for the symbol "this".

gdb/testsuite/ChangeLog:

	* gdb.fortran/derived-types.exp (result_line, result_line_2):
	New variables.
	(print this%a, print this%b, print this): New tests.
	* gdb.fortran/derived-types.f90 (this): New object and
	initialization.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR python/15620, PR python/18620 - breakpoint events in Python
@ 2016-07-13 21:51 sergiodj+buildbot
  2016-07-21 19:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-13 21:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dac790e1b9048a318e1882979d7188d82c3bd757 ***

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

PR python/15620, PR python/18620 - breakpoint events in Python

This patch adds some breakpoint events to Python.  In particular,
there is a creation event that is emitted when a breakpoint is
created; a modification event that is emitted when a breakpoint
changes somehow; and a deletion event that is emitted when a
breakpoint is deleted.

In this patch, the event's payload is the breakpoint itself.  I
considered making a new event type to hold the breakpoint, but I
didn't see a need.  Still, I thought I would mention this as a spot
where some other choice is possible.

Built and regtested on x86-64 Fedora 23.

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

	PR python/15620, PR python/18620:
	* python/py-evts.c (gdbpy_initialize_py_events): Call
	add_new_registry for new events.
	* python/py-events.h (events_object) <breakpoint_created,
	breakpoint_deleted, breakpoint_modified>: New fields.
	* python/py-breakpoint.c (gdbpy_breakpoint_created): Emit the
	breakpoint changed event.
	(gdbpy_breakpoint_deleted): Emit the breakpoint deleted event.
	(gdbpy_breakpoint_modified): New function.
	(gdbpy_initialize_breakpoints): Attach to the breakpoint modified
	observer.

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

	PR python/15620, PR python/18620:
	* python.texi (Events In Python): Document new breakpoint events.

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

	PR python/15620, PR python/18620:
	* gdb.python/py-breakpoint.exp (connect_event, check_last_event)
	(test_bkpt_events): New procs.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use do_self_tests in selftest.exp
@ 2016-07-19 10:01 sergiodj+buildbot
  2016-07-23 22:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-19 10:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f25827c194fe9894f2c65f7e1101854022be4328 ***

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

Use do_self_tests in selftest.exp

This patch uses do_self_tests to simplify selftest.exp.  It doesn't
change the tests except the order,

-PASS: gdb.gdb/selftest.exp: Disassemble main
 PASS: gdb.gdb/selftest.exp: breakpoint in captured_main
+PASS: gdb.gdb/selftest.exp: run until breakpoint at captured_main
+PASS: gdb.gdb/selftest.exp: Disassemble main
 PASS: gdb.gdb/selftest.exp: set interrupt character in test_with_self
 PASS: gdb.gdb/selftest.exp: set listsize to 1
-PASS: gdb.gdb/selftest.exp: run until breakpoint at captured_main

gdb/testsuite:

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

	* gdb.gdb/selftest.exp: Remove checks on is_remote and isnative.
	(test_with_self): Remove some code.  Remove argument executable.
	(top-level): Use do_self_tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Get "num" as unsigned in ctf
@ 2016-07-22 17:58 sergiodj+buildbot
  2016-07-27 11:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-07-22 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eed2386e45968fa4fee8d093895f4789044fb077 ***

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

Get "num" as unsigned in ctf

I see the following fail due to the warning,

-trace-frame-collected^M
[warning] Extracting signed value from an unsigned int (num)^M
....
FAIL: gdb.trace/mi-trace-frame-collected.exp: ctf: -trace-frame-collected

In ctf metadata, "num" in "tsv" is defined as unint32_t,

  ctf_save_write_metadata (&writer->tcs,
			   "event {\n\tname = \"tsv\";\n\tid = %u;\n"
			   "\tfields := struct { \n"
			   "\t\tuint64_t val;\n"
			   "\t\tuint32_t num;\n"
			   "\t};\n"
			   "};\n", CTF_EVENT_ID_TSV);

so we should read it as unsigned.  The patch below fixes the fail by
changing to bt_ctf_get_uint64.

gdb:

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

	* ctf.c (ctf_traceframe_info): Call bt_ctf_get_uint64 rather than
	bt_ctf_get_int64.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <7bd374a44d1db21b54a9a52ecde1d064cdaa8cd1@gdb-build>]
* [binutils-gdb] Swap "single-process" and "multi-process" in process-dies-while-detaching.exp
@ 2016-08-01 13:20 sergiodj+buildbot
  2016-08-01 15:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 13:20 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

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

This patch is to swap them.

gdb/testsuite:

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Determine target description for native aarch64
@ 2016-08-04 11:45 sergiodj+buildbot
  2016-08-04 15:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-04 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f67973b4280cfd045e632a3340becd16e43b4b1 ***

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

Determine target description for native aarch64

I find the following test fail when I test native aarch64 gdb with
arm program,

(gdb) PASS: gdb.base/attach-pie-noexec.exp: attach
set architecture arm^M
warning: Selected architecture arm is not compatible with reported target architecture aarch64^M
Architecture `arm' not recognized.^M
The target architecture is set automatically (currently aarch64)^M
(gdb) FAIL: gdb.base/attach-pie-noexec.exp: set architecture arm

GDB thinks the target is aarch64, but it isn't.  Nowadays, we are
using some entries AT_PHENT and AT_HWCAP in auxv to determine whether
the process is a 32-bit arm one or 64-bit aarch64 one, and get the
right gdbarch.  However, in the process of parsing auxv (in
inf_ptrace_auxv_parse), the size of int and data pointer of
target_gdbarch is used.  If debug program exists (in most of cases),
target_gdbarch is already set according to the debug program, which
is arm in my case.  Then, GDB can parse auxv successfully.  However,
in gdb.base/attach-pie-noexec.exp, the debug program is removed,
target_gdbarch is aarch64 when GDB parse auxv, so GDB can't parse
it successfully.

Instead of using auxv, we check the return value of ptrace NT_ARM_VFP.
If the program is an arm process, NT_ARM_VFP is OK, otherwise, error
is returned.

Additionally, we only return tdesc_arm_with_neon for arm process,
because neon is mandatory on ARMv8.

gdb:

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

	* aarch64-linux-nat.c (tdesc_arm_with_vfpv3): Remove the
	declaration.
	(aarch64_linux_read_description): Remove code on getting
	auxv and select target description on it.  Select target
	description by the result of NT_ARM_VFP ptrace request.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove unused cli_command_loop declaration
@ 2016-08-05 22:57 sergiodj+buildbot
  2016-08-07 20:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-05 22:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c632e428c2fd707b83a2c61e0b25b473e3d7d18e ***

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

Remove unused cli_command_loop declaration

This declaration is not used anymore.

gdb/ChangeLog:

	* event-top.h (cli_command_loop): Remove.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Correct the calculation of the use_counts of merged .got entries.
@ 2016-08-09 20:38 sergiodj+buildbot
  2016-08-09 22:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 20:38 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions
@ 2016-08-09 22:30 sergiodj+buildbot
  2016-08-09 22:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 22:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f348d89aeccaf3eb613e2f31a823baa64300bf88 ***

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

Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions

gdb's (or gdbserver's) own signal handling should not interfere with
the signal dispositions their spawned children inherit.  However, it
currently does.  For example, some paths in gdb cause SIGPIPE to be
set to SIG_IGN, and as consequence, the child starts with SIGPIPE to
set to SIG_IGN too, even though gdb was started with SIGPIPE set to
SIG_DFL.

This is because the exec family of functions does not reset the signal
disposition of signals that are set to SIG_IGN:

  http://pubs.opengroup.org/onlinepubs/7908799/xsh/execve.html

  Signals set to the default action (SIG_DFL) in the calling process
  image are set to the default action in the new process
  image. Signals set to be ignored (SIG_IGN) by the calling process
  image are set to be ignored by the new process image. Signals set to
  be caught by the calling process image are set to the default action
  in the new process image (see <signal.h>).

And neither does it reset signal masks or flags.

In order to be transparent, when spawning new child processes to debug
(with "run", etc.), reset signal actions and mask back to what was
originally inherited from gdb/gdbserver's parent, just before execing
the target program to debug.

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

	PR gdb/18653
	* Makefile.in (SFILES): Add
	common/signals-state-save-restore.c.
	(HFILES_NO_SRCDIR): Add common/signals-state-save-restore.h.
	(COMMON_OBS): Add signals-state-save-restore.o.
	(signals-state-save-restore.o): New rule.
	* configure: Regenerate.
	* fork-child.c: Include "signals-state-save-restore.h".
	(fork_inferior): Call restore_original_signals_state.
	* main.c: Include "signals-state-save-restore.h".
	(captured_main): Call save_original_signals_state.
	* common/common.m4: Add sigaction to AC_CHECK_FUNCS checks.
	* common/signals-state-save-restore.c: New file.
	* common/signals-state-save-restore.h: New file.

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

	PR gdb/18653
	* Makefile.in (OBS): Add signals-state-save-restore.o.
	(signals-state-save-restore.o): New rule.
	* config.in: Regenerate.
	* configure: Regenerate.
	* linux-low.c: Include "signals-state-save-restore.h".
	(linux_create_inferior): Call
	restore_original_signals_state.
	* server.c: Include "dispositions-save-restore.h".
	(captured_main): Call save_original_signals_state.

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

	PR gdb/18653
	* gdb.base/signals-state-child.c: New file.
	* gdb.base/signals-state-child.exp: New file.
	* gdb.gdb/selftest.exp (do_steps_and_nexts): Add new pattern.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR mi/20431 - Missing MI prompts after sync execution MI command (-exec-continue, etc.) errors
@ 2016-08-10  0:26 sergiodj+buildbot
  2016-08-10  1:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-10  0:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80614914274f7166baea2ec656aec6a949869324 ***

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

Fix PR mi/20431 - Missing MI prompts after sync execution MI command (-exec-continue, etc.) errors

gdb 7.11 introduced an MI regression: a failing MI sync execution
command misses printing the MI prompt, and then all subsequent command
miss it too:

 $ gdb-7.11.1 -i=mi
 [...]
 p 1
 &"p 1\n"
 ~"$1 = 1"
 ~"\n"
 ^done
 (gdb)                                        <<< prompted ok
 -exec-continue
 ^error,msg="The program is not being run."   <<< missing prompt after this
 print 1
 &"print 1\n"
 ~"$2 = 1"
 ~"\n"
 ^done                                        <<< missing prompt after this


gdb 7.10.1 behaved correctly, even with "set mi-async on":

 -exec-continue
 ^error,msg="The program is not being run."
 (gdb)                                        <<< prompted ok

etc.

Bisecting points at:

  commit 0b333c5e7d6c
  Author: Pedro Alves <palves@redhat.com>
  Date:   Wed Sep 9 18:23:23 2015 +0100

      Merge async and sync code paths some more
  [...]

The problem is that when an exception is thrown, we leave the prompt
state set to PROMPT_BLOCKED, and then mi_execute_command_input_handler
doesn't print the prompt.  It used to work because before that patch,
we happened to skip disabling stdin if the current target didn't do
async (which it never does before execution).

I was surprised to find that this bug isn't caught by the testsuite,
so I made a thorough test that tests all combinations of pairs of:

 - a failing synchronous execution command
 - a failing non-execution command
 - a non-failing command

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

	PR mi/20431
	* mi/mi-main.c (mi_execute_command): Enable input and set prompt
	state to PROMPT_NEEDED.

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

	PR mi/20431
	* gdb.mi/mi-cmd-error.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR gdb/20418 - Problems with synchronous commands and new-ui
@ 2016-08-10  1:19 sergiodj+buildbot
  2016-08-10  3:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-10  1:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3eb7562a983bab4c768983bcd85708852d171121 ***

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

Fix PR gdb/20418 - Problems with synchronous commands and new-ui

When executing commands on a secondary UI running the MI interpreter,
some commands that should be synchronous are not.  MI incorrectly
continues processing input right after the synchronous command is
sent, before the target stops.

The problem happens when we emit MI async events (=library-loaded,
etc.), and we go about restoring the previous terminal state, we end
up calling target_terminal_ours, which incorrectly always installs the
current UI's input_fd in the event loop...  That is, code like this:

   old_chain = make_cleanup_restore_target_terminal ();
   target_terminal_ours_for_output ();

   fprintf_unfiltered (mi->event_channel, "library-loaded");

...

   do_cleanups (old_chain);

The fix is to move the add_file_handler/delete_file_handler calls out
of target_terminal_$foo, making these completely no-ops unless called
with the main UI as current UI.

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

	PR gdb/20418
	* event-top.c (ui_register_input_event_handler)
	(ui_unregister_input_event_handler): New functions.
	(async_enable_stdin): Register input in the event loop.
	(async_disable_stdin): Unregister input from the event loop.
	(gdb_setup_readline): Register input in the event loop.
	* infrun.c (check_curr_ui_sync_execution_done): Register input in
	the event loop.
	* target.c (target_terminal_inferior): Don't unregister input from
	the event loop.
	(target_terminal_ours): Don't register input in the event loop.
	* target.h (target_terminal_inferior)
	(target_terminal_ours_for_output, target_terminal_ours): Update
	comments.
	* top.h (ui_register_input_event_handler)
	(ui_unregister_input_event_handler): New declarations.
	* utils.c (ui_unregister_input_event_handler_cleanup)
	(prepare_to_handle_input): New functions.
	(defaulted_query, prompt_for_continue): Use
	prepare_to_handle_input.

gdb/testsuite/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>
	    Simon Marchi  <simon.marchi@ericsson.com>

	PR gdb/20418
	* gdb.mi/new-ui-mi-sync.c, gdb.mi/new-ui-mi-sync.exp: New files.
	* lib/mi-support.exp (mi_expect_interrupt): Remove anchors.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Quiet ARI gettext checks
@ 2016-08-10 21:20 sergiodj+buildbot
  2016-08-10 22:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-10 21:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 669f9429c7b5a9e827497c5ad70efb6a570c8c7d ***

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

Quiet ARI gettext checks

The ARI complains about this new file:

 common/signals-state-save-restore.c:46: warning: gettext: All messages should be marked up with _.
 common/signals-state-save-restore.c:59: warning: gettext: All messages should be marked up with _.
 common/signals-state-save-restore.c:87: warning: gettext: All messages should be marked up with _.
 common/signals-state-save-restore.c:92: warning: gettext: All messages should be marked up with _.

Since these are untranslatable strings, use () instead of _().

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

	* common/signals-state-save-restore.c
	(save_original_signals_state, restore_original_signals_state):
	Wrap perror_with_name arguments with '()'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Support setting thread names (MS-Windows)
@ 2016-08-11  0:35 sergiodj+buildbot
  2016-08-11  0:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  0:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24cdb46e9f0a694b4fbc11085e094857f08c0419 ***

Author:   <lrn1986@gmail.com>
Branch: master
Commit: 24cdb46e9f0a694b4fbc11085e094857f08c0419

Support setting thread names (MS-Windows)

This is done by catching an exception number 0x406d1388 (it has no
documented name, though MSDN dubs it "MS_VC_EXCEPTION" in one code
example), which is thrown by the program.  The exception record
contains an ID of a thread and a name to give it.

This requires rolling back some changes in handle_exception(), which
now again returns more than two distinct values.  The new
HANDLE_EXCEPTION_IGNORED value means that gdb should just continue,
without returning the thread ID up the stack (which would result in
further handling of the exception, which is not what we want).

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

	* windows-nat.c (MS_VC_EXCEPTION): New define.
	(handle_exception_result): New enum.
	(windows_delete_thread): Free the thread's name.
	(handle_exception): Handle MS_VC_EXCEPTION.
	(get_windows_debug_event): Handle HANDLE_EXCEPTION_IGNORED.
	(windows_thread_name): New function.
	(windows_target): Install it as to_thread_name method.
	* NEWS: Mention the thread naming support on MS-Windows.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix missing files for ld when test suite not compiled in the source directory
@ 2016-08-20  9:29 sergiodj+buildbot
  2016-08-22 19:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-20  9:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20c2c024c1e89e402a57e8c3577fb9777709d9a4 ***

Author: Carl E. Love <carll@oc4738070240.ibm.com>
Branch: master
Commit: 20c2c024c1e89e402a57e8c3577fb9777709d9a4

Fix missing files for ld when test suite not compiled in the source directory

This patch fixes an issues with six test suite expect files that do not
run correctly when the test suite is not built in the source directory.  The
issue is these tests are not using the current "standard_testfile" call
but rather using the older set command to initialize the "testfile",
"srcfile" and "binprefix" variables or are missing the set for the
"binprefix" variable.

-----------------------------------------------

gdb/testsuite/ChangeLog

2016-08-19  Carl Love  <cel@us.ibm.com>

	* gdb.arch/altivec-regs.exp: Use standard_testfile instead of
	maintaining separate logic for constructing the output path.
	* gdb.arch/powerpc-d128-regs.exp: Likewise.
	* gdb.arch/ppc-dfp.exp: Likewise.
	* gdb.arch/ppc-fp.exp: Likewise.
	* gdb.arch/vsx-regs.exp: Likewise.
	* gdb.arch/altivec-abi.exp: Likewise, plus added local variable
	binprefix for generating the additional binary files.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Allow resetting an empty inferior-tty
@ 2016-08-24 20:24 sergiodj+buildbot
  2016-08-25  9:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-08-24 20:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a1ddfa6b67201bb06f51fb47b56096e81bec5c0 ***

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

Allow resetting an empty inferior-tty

This patch allows the user to set the inferior-tty to "empty", in order
to come back to the default behaviour of using the same tty as gdb is
using.

This is already supported in MI (and tested in gdb.mi/mi-basics.exp).

I added a new test, set-inferior-tty.exp, where I test only the setting
and unsetting of the parameter.  It would be nice to actually test that
the inferior output properly goes to the separate tty, but that will be
for another day.

gdb/ChangeLog:

	* infcmd.c (set_inferior_io_terminal): Set inferior terminal to
	NULL if terminal_name is an empty string.
	(_initialize_infcmd): Make the argument of "set inferior-tty"
	optional, mention it in the help doc.

gdb/doc/ChangeLog:

	* gdb.texinfo (Input/Output): Mention possibility to unset
	inferior-tty.

gdb/testsuite/ChangeLog:

	* gdb.base/set-inferior-tty.exp: New file.
	* gdb.base/set-inferior-tty.c: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use target_continue{, _no_signal} instead of target_resume
@ 2016-09-02  9:02 sergiodj+buildbot
  2016-09-02  8:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-09-02  9:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 049a857091cff98371b5688140832a3cf767153c ***

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

Use target_continue{,_no_signal} instead of target_resume

This commit implements a new function, target_continue, on top of the
target_resume function.  Then, it replaces all calls to target_resume
by calls to target_continue or to the already existing
target_continue_no_signal.

This is one of the (many) necessary steps needed to consolidate the
target interface between GDB and gdbserver.  In particular, I am
interested in the impact this change will have on the unification of
the fork_inferior function (which I have been working on).

Tested on the BuildBot, no regressions introduced.

gdb/gdbserver/ChangeLog:
2016-09-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* server.c (start_inferior): New variable 'ptid'.  Replace calls
	to the_target->resume by target_continue{,_no_signal}, depending
	on the case.
	* target.c (target_stop_and_wait): Call target_continue_no_signal
	instead of the_target->resume.
	(target_continue): New function.

gdb/ChangeLog:
2016-09-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* fork-child.c (startup_inferior): Replace calls to target_resume
	by target_continue{,_no_signal}, depending on the case.
	* linux-nat.c (cleanup_target_stop): Call
	target_continue_no_signal instead of target_resume.
	* procfs.c (procfs_wait): Likewise.
	* target.c (target_continue): New function.
	* target/target.h (target_continue): New prototype.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Handle DW_OP_form_tls_address
@ 2016-09-03 12:46 sergiodj+buildbot
  2016-09-05 18:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-09-03 12:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4aa4e28bdcf5f0d733def62b542fea11d5f219d5 ***

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

Handle DW_OP_form_tls_address

Currently gdb supports DW_OP_GNU_push_tls_address, but not
DW_OP_form_tls_address.  I think it would be better if the toolchain
as a whole moved to using the standard opcode, and the prerequisite to
this is getting gdb to recognize it.

GCC can sometimes emit DW_OP_form_tls_address for emultls targets.  As
far as I know, nobody has ever tried this with gdb (since it wouldn't
work at all).

I don't think there's a major drawback to using a single opcode for
all targets, because computing the location of a thread-local is
already target specific.

This is PR gdb/11616.

I don't know how to write a test case for this; though it's worth
noting that there aren't explicit tests for DW_OP_GNU_push_tls_address
either -- and if I change GCC, these paths will be tested to the same
extent they are now.

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

	PR gdb/11616:
	* dwarf2read.c (decode_locdesc): Handle DW_OP_form_tls_address.
	* dwarf2loc.c (dwarf2_compile_expr_to_ax): Handle
	DW_OP_form_tls_address.
	(locexpr_describe_location_piece): Likewise.
	* dwarf2expr.h (struct dwarf_expr_context_funcs): Update comment.
	* dwarf2expr.c (execute_stack_op): Handle DW_OP_form_tls_address.
	(ctx_no_get_tls_address): Mention DW_OP_form_tls_address.
	* compile/compile-loc2c.c (struct insn_info): Update comment.
	(compute_stack_depth_worker): Handle DW_OP_form_tls_address.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Removed redundant line remote-utils.c
@ 2016-09-05 19:41 sergiodj+buildbot
  2016-09-05 20:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-09-05 19:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1da6748f560ec19173d5d7766e0d497e8a0f1e4 ***

Author: Akash Trehan <akash.trehan123@gmail.com>
Branch: master
Commit: c1da6748f560ec19173d5d7766e0d497e8a0f1e4

Removed redundant line remote-utils.c

2016-09-02  Akash Trehan  <akash.trehan123@gmail.com>

gdb/gdbserver/ChangeLog:
    PR gdb/19495
    * remote-utils.c (relocate_instruction): Remove redundant strcpy()
    call writing data to own_buf.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add missing format for built-in floating-point types
@ 2016-09-06 23:37 sergiodj+buildbot
  2016-09-07 12:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 23:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49f190bcb7f074ea2e27d4e967e4fae9ed7dafb6 ***

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

Add missing format for built-in floating-point types

Many callers of init_float_type and arch_float_type still pass a NULL
floatformat.  This commit changes those callers where the floatformat
that is supposed to be use is obvious.  There are two categories where
this is the case:

- A number of built-in types are intended to match the platform ABI
  floating-point types (i.e. types that use gdbarch_float_bit etc.).
  Those places should use the platform ABI floating-point formats
  defined via gdbarch_float_format etc.

- A number of language built-in types should simply use IEEE floating-
  point formats, since the language actually defines that this is the
  format that must be used to implement floating-point types for this
  language.  (This affects Java, Go, and Rust.)  The same applies for
  to the predefined "RS/6000" stabs floating-point built-in types.

gdb/ChangeLog:

	* ada-lang.c (ada_language_arch_info): Use gdbarch-provided
	platform ABI floating-point formats for built-in types.
	* d-lang.c (build_d_types): Likewise.
	* f-lang.c (build_fortran_types): Likewise.
	* m2-lang.c (build_m2_types): Likewise.
	* mdebugread.c (basic_type): Likewise.

	* go-lang.c (build_go_types): Use IEEE floating-point formats
	for language built-in types as mandanted by the language.
	* jv-lang.c (build_java_types): Likewise.
	* rust-lang.c (rust_language_arch_info): Likewise.
	* stabsread.c (rs6000_builtin_type): Likewise.

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Introduce make_cleanup_restore_current_ui
@ 2016-09-07  5:56 sergiodj+buildbot
  2016-09-09 18:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  5:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a025b477cc466112af0b120c5f2bf5d62a62017e ***

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

Introduce make_cleanup_restore_current_ui

Just a tidy, no functional changes.

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

	* event-top.c (restore_ui_cleanup): Now static.
	(make_cleanup_restore_current_ui): New function.
	(switch_thru_all_uis_init): Use it.
	* infcall.c (call_thread_fsm_should_stop): Use it.
	* infrun.c (fetch_inferior_event): Use it.
	* top.c (new_ui_command): Use it.
	* top.h (restore_ui_cleanup): Delete declaration.
	(make_cleanup_restore_current_ui): New declaration.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Modify POWER9 support to match final ISA 3.0 documentation.
@ 2016-09-15 21:47 sergiodj+buildbot
  2016-09-15 21:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-09-15 21:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd486b633e87f8ab2977592d56a6d98168814e2e ***

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

Modify POWER9 support to match final ISA 3.0 documentation.

opcodes/
	* ppc-opc.c (powerpc_opcodes) <slbiag>: New mnemonic.
	<addex., brd, brh, brw, lwzmx, nandxor, rldixor, setbool,
	xor3>: Delete mnemonics.
	<cp_abort>: Rename mnemonic from ...
	<cpabort>: ...to this.
	<setb>: Change to a X form instruction.
	<sync>: Change to 1 operand form.
	<copy>: Delete mnemonic.
	<copy_first>: Rename mnemonic from ...
	<copy>: ...to this.
	<paste, paste.>: Delete mnemonics.
	<paste_last>: Rename mnemonic from ...
	<paste.>: ...to this.

gas/
	* testsuite/gas/ppc/power9.d <slbiag, cpabort> New tests.
	<addex., brd, brh, brw, lwzmx, nandxor, rldixor, setbool,
	xor3, cp_abort, copy_first, paste, paste_last, sync>: Remove tests.
	<copy, paste.>: Update tests.
	* testsuite/gas/ppc/power9.s: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Fix std::{min, max}-related build breakage on 32-bit hosts
@ 2016-09-19  6:16 sergiodj+buildbot
  2016-09-20 13:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-09-19  6:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 768adc05c44c7e8b5c0f9ca5ad3ca96657715293 ***

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

gdb: Fix std::{min, max}-related build breakage on 32-bit hosts

Building on a 32-bit host fails currently with errors like:

  .../src/gdb/exec.c: In function target_xfer_status section_table_read_available_memory(gdb_byte*, ULONGEST, ULONGEST, ULONGEST*):
  .../src/gdb/exec.c:801:54: error: no matching function for call to min(ULONGEST, long unsigned int)
      end = std::min (offset + len, r->start + r->length);
							^
  In file included from /usr/include/c++/5.3.1/algorithm:61:0,
		   from .../src/gdb/exec.c:46:
  /usr/include/c++/5.3.1/bits/stl_algobase.h:195:5: note: candidate: template<class _Tp> const _Tp& std::min(const _Tp&, const _Tp&)
       min(const _Tp& __a, const _Tp& __b)
       ^
  /usr/include/c++/5.3.1/bits/stl_algobase.h:195:5: note:   template argument deduction/substitution failed:
  .../src/gdb/exec.c:801:54: note:   deduced conflicting types for parameter const _Tp (long long unsigned int and long unsigned int)
      end = std::min (offset + len, r->start + r->length);
							^
  In file included from /usr/include/c++/5.3.1/algorithm:61:0,
		   from .../src/gdb/exec.c:46:
  /usr/include/c++/5.3.1/bits/stl_algobase.h:243:5: note: candidate: template<class _Tp, class _Compare> const _Tp& std::min(const _Tp&, const _Tp&, _Compare)
       min(const _Tp& __a, const _Tp& __b, _Compare __comp)
       ^

The problem is that the std::min/std::max function templates use the
same type for both parameters.  When the argument types are different,
the compiler can't automatically deduce which template specialization
to pick from the arguments' types.

Fix that by specifying the specialization we want explicitly.

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

	* breakpoint.c (hardware_watchpoint_inserted_in_range): Explicitly
	specify the std:min/std::max specialization.
	* exec.c (section_table_read_available_memory): Likewise.
	* remote.c (remote_read_qxfer): Likewise.
	* target.c (simple_verify_memory): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Consolidate target_mourn_inferior between GDB and gdbserver
@ 2016-09-19 16:45 sergiodj+buildbot
  2016-09-20 17:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-09-19 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc1e6c81d5b77d78282c47f6fd7f697e564a6eb6 ***

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

Consolidate target_mourn_inferior between GDB and gdbserver

This patch consolidates the API of target_mourn_inferior between GDB
and gdbserver, in my continuing efforts to make sharing the
fork_inferior function possible between both.

GDB's version of the function did not care about the inferior's ptid
being mourned, but gdbserver's needed to know this information.  Since
it actually makes sense to pass the ptid as an argument, instead of
depending on a global value directly (which GDB's version did), I
decided to make the generic API to accept it.  I then went on and
extended all calls being made on GDB to include a ptid argument (which
ended up being inferior_ptid most of the times, anyway), and now we
have a more sane interface.

On GDB's side, after talking to Pedro a bit about it, we decided that
just an assertion to make sure that the ptid being passed is equal to
inferior_ptid would be enough for now, on the GDB side.  We can remove
the assertion and perform more operations later if we ever pass
anything different than inferior_ptid.

Regression tested on our BuildBot, everything OK.

I'd appreciate a special look at gdb/windows-nat.c's modification
because I wasn't really sure what to do there.  It seemed to me that
maybe I should build a ptid out of the process information there, but
then I am almost sure the assertion on GDB's side would trigger.

gdb/ChangeLog:
2016-09-19  Sergio Durigan Junior  <sergiodj@redhat.com>

	* darwin-nat.c (darwin_kill_inferior): Adjusting call to
	target_mourn_inferior to include ptid_t argument.
	* fork-child.c (startup_inferior): Likewise.
	* gnu-nat.c (gnu_kill_inferior): Likewise.
	* inf-ptrace.c (inf_ptrace_kill): Likewise.
	* infrun.c (handle_inferior_event_1): Likewise.
	* linux-nat.c (linux_nat_attach): Likewise.
	(linux_nat_kill): Likewise.
	* nto-procfs.c (interrupt_query): Likewise.
	(procfs_interrupt): Likewise.
	(procfs_kill_inferior): Likewise.
	* procfs.c (procfs_kill_inferior): Likewise.
	* record.c (record_mourn_inferior): Likewise.
	* remote-sim.c (gdbsim_kill): Likewise.
	* remote.c (remote_detach_1): Likewise.
	(remote_kill): Likewise.
	* target.c (target_mourn_inferior): Change declaration to accept
	new ptid_t argument; use gdb_assert on it.
	* target.h (target_mourn_inferior): Move function prototype from
	here...
	* target/target.h (target_mourn_inferior): ... to here.  Adjust it
	to accept new ptid_t argument.
	* windows-nat.c (get_windows_debug_event): Adjusting call to
	target_mourn_inferior to include ptid_t argument.

gdb/gdbserver/ChangeLog:
2016-09-19  Sergio Durigan Junior  <sergiodj@redhat.com>

	* server.c (start_inferior): Call target_mourn_inferior instead of
	mourn_inferior; pass ptid_t argument to it.
	(resume): Likewise.
	(handle_target_event): Likewise.
	* target.c (target_mourn_inferior): New function.
	* target.h (mourn_inferior): Delete macro.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Disallow 3-operand cmp[l][i] for ppc64
@ 2016-09-29 17:39 sergiodj+buildbot
  2016-09-29 17:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-09-29 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a5721ba270ddf860e0e5a45bba456214e8eac2be ***

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

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

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

L field of dcbf and wclr is 2 bits.

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Pass link_info to _bfd_merge_private_bfd_data
@ 2016-10-07  2:07 sergiodj+buildbot
  2016-10-08 20:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-07  2:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50e03d47b77d5730f96f6b6bb66187654e66c797 ***

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

Pass link_info to _bfd_merge_private_bfd_data

Most BFD linker functions take a bfd_link_info param, which reinforces
the fact that they are linker functions and allow access to linker
callbacks, eg. einfo for printing errors.  I was going to use einfo
for --fatal-warnings support before I decided a better way was the
patch commit 4519d071.

bfd/
	* targets.c (bfd_target <_bfd_merge_private_bfd_data>): Replace
	obfd param with struct bfd_link_info param.  Update all callers.
	* linker.c (bfd_merge_private_bfd_data): Likewise.
	(_bfd_generic_verify_endian_match): Likewise.
	* aoutf1.h (sunos_merge_private_bfd_data): Likewise.
	* coff-arm.c (coff_arm_merge_private_bfd_data): Likewise.
	* elf-attrs.c (_bfd_elf_merge_object_attributes): Likewise.
	* elf-bfd.h (_bfd_elf_ppc_merge_fp_attributes): Likewise.
	(_bfd_elf_merge_object_attributes): Likewise.
	* elf-m10300.c (_bfd_mn10300_elf_merge_private_bfd_data): Likewise.
	* elf-s390-common.c (elf_s390_merge_obj_attributes): Likewise.
	* elf32-arc.c (arc_elf_merge_private_bfd_data): Likewise.
	* elf32-arm.c (elf32_arm_merge_eabi_attributes): Likewise.
	(elf32_arm_merge_private_bfd_data): Likewise.
	* elf32-bfin.c (elf32_bfin_merge_private_bfd_data): Likewise.
	* elf32-cr16.c (_bfd_cr16_elf_merge_private_bfd_data): Likewise.
	* elf32-cris.c (cris_elf_merge_private_bfd_data): Likewise.
	* elf32-frv.c (frv_elf_merge_private_bfd_data): Likewise.
	* elf32-h8300.c (elf32_h8_merge_private_bfd_data): Likewise.
	* elf32-i370.c (i370_elf_merge_private_bfd_data): Likewise.
	* elf32-iq2000.c (iq2000_elf_merge_private_bfd_data): Likewise.
	* elf32-m32c.c (m32c_elf_merge_private_bfd_data): Likewise.
	* elf32-m32r.c (m32r_elf_merge_private_bfd_data): Likewise.
	* elf32-m68hc1x.c (_bfd_m68hc11_elf_merge_private_bfd_data): Likewise.
	* elf32-m68hc1x.h (_bfd_m68hc11_elf_merge_private_bfd_data): Likewise.
	* elf32-m68k.c (elf32_m68k_merge_private_bfd_data): Likewise.
	* elf32-mcore.c (mcore_elf_merge_private_bfd_data): Likewise.
	* elf32-mep.c (mep_elf_merge_private_bfd_data): Likewise.
	* elf32-msp430.c (elf32_msp430_merge_mspabi_attributes): Likewise.
	(elf32_msp430_merge_private_bfd_data): Likewise.
	* elf32-mt.c (mt_elf_merge_private_bfd_data): Likewise.
	* elf32-nds32.c (nds32_elf_merge_private_bfd_data): Likewise.
	* elf32-nios2.c (nios2_elf32_merge_private_bfd_data): Likewise.
	* elf32-or1k.c (elf32_or1k_merge_private_bfd_data): Likewise.
	* elf32-ppc.c (_bfd_elf_ppc_merge_fp_attributes): Likewise.
	(ppc_elf_merge_obj_attributes): Likewise.
	(ppc_elf_merge_private_bfd_data): Likewise.
	* elf32-rl78.c (rl78_elf_merge_private_bfd_data): Likewise.
	* elf32-rx.c (rx_elf_merge_private_bfd_data): Likewise.
	* elf32-s390.c (elf32_s390_merge_private_bfd_data): Likewise.
	* elf32-score.c (s3_elf32_score_merge_private_bfd_data): Likewise.
	(elf32_score_merge_private_bfd_data): Likewise.
	* elf32-score.h (s7_elf32_score_merge_private_bfd_data): Likewise.
	* elf32-score7.c (s7_elf32_score_merge_private_bfd_data): Likewise.
	* elf32-sh.c (sh_merge_bfd_arch, sh_elf_merge_private_data): Likewise.
	* elf32-sh64.c (sh64_elf_merge_private_data): Likewise.
	* elf32-sparc.c (elf32_sparc_merge_private_bfd_data): Likewise.
	* elf32-tic6x.c (elf32_tic6x_merge_attributes): Likewise.
	(elf32_tic6x_merge_private_bfd_data): Likewise.
	* elf32-v850.c (v850_elf_merge_private_bfd_data): Likewise.
	* elf32-vax.c (elf32_vax_merge_private_bfd_data): Likewise.
	* elf32-visium.c (visium_elf_merge_private_bfd_data): Likewise.
	* elf32-xtensa.c (elf_xtensa_merge_private_bfd_data): Likewise.
	* elf64-ia64-vms.c (elf64_ia64_merge_private_bfd_data): Likewise.
	* elf64-ppc.c (ppc64_elf_merge_private_bfd_data): Likewise.
	* elf64-s390.c (elf64_s390_merge_private_bfd_data): Likewise.
	* elf64-sh64.c (sh_elf64_merge_private_data): Likewise.
	* elf64-sparc.c (elf64_sparc_merge_private_bfd_data): Likewise.
	* elfnn-aarch64.c (elfNN_aarch64_merge_private_bfd_data): Likewise.
	* elfnn-ia64.c (elfNN_ia64_merge_private_bfd_data): Likewise.
	* elfxx-mips.c (mips_elf_merge_obj_e_flags): Likewise.
	(mips_elf_merge_obj_attributes): Likewise.
	(_bfd_mips_elf_merge_private_bfd_data): Likewise.
	* elfxx-mips.h (_bfd_mips_elf_merge_private_bfd_data): Likewise.
	* elfxx-sparc.c (_bfd_sparc_elf_merge_private_bfd_data): Likewise.
	* elfxx-sparc.h (_bfd_sparc_elf_merge_private_bfd_data): Likewise.
	* elfxx-target.h (bfd_elfNN_bfd_merge_private_bfd_data): Likewise.
	* elfxx-tilegx.c (_bfd_tilegx_elf_merge_private_bfd_data): Likewise.
	* elfxx-tilegx.h (_bfd_tilegx_elf_merge_private_bfd_data): Likewise.
	* libbfd-in.h (_bfd_generic_bfd_merge_private_bfd_data): Likewise.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
ld/
	* ldlang.c (lang_check): Update bfd_merge_private_bfd_data call.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] python: accept address and explicit locations in gdb.decode_line
@ 2016-10-07  7:22 sergiodj+buildbot
  2016-10-08 21:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-07  7:22 UTC (permalink / raw)
  To: gdb-testers

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

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

python: accept address and explicit locations in gdb.decode_line

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] PR target/20667, fix disassembler for the "special" optional SYS_Rt operand for "ic"/"tlbi"
@ 2016-10-07 10:19 sergiodj+buildbot
  2016-10-09  0:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-07 10:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 362c0c4d9cc9f320d1e85755404879a13ebed91a ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 362c0c4d9cc9f320d1e85755404879a13ebed91a

[AArch64] PR target/20667, fix disassembler for the "special" optional SYS_Rt operand for "ic"/"tlbi"

gas/
	PR target/20667
	* testsuite/gas/aarch64/sys-rt-reg.s: Test source for instructions
	using SYS_Rt reg.
	* testsuite/gas/aarch64/sys-rt-reg.d: New testcase.

opcodes/
	PR target/20667
	* aarch64-opc.c (aarch64_print_operand): Always print operand if
	it's available.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Set regdir in tdesc-regs.exp or arm
@ 2016-10-07 10:50 sergiodj+buildbot
  2016-10-08 23:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-07 10:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d0e042a8321cca82cce521afd276a8494385ae3 ***

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

Set regdir in tdesc-regs.exp or arm

0a69eedb (Clean up the XML files for ARM) moves arm-*.xml files to
arm/ directory, so need update gdb.xml/tdesc-regs.exp accordingly.

gdb/testsuite:

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

	* gdb.xml/tdesc-regs.exp: Set regdir to "arm/".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] ui-out.c: Remove unused parameter to push_level
@ 2016-10-09  0:26 sergiodj+buildbot
  2016-10-09  4:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-09  0:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49d06418ada11004ca1cdc0ec5847358e83fc67a ***

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

ui-out.c: Remove unused parameter to push_level

The parameter "id" is unused.

gdb/ChangeLog:

	* ui-out.c (push_level): Remove "id" parameter.
	(ui_out_begin): Update call.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove v850_dbtrap_breakpoint_from_pc
@ 2016-10-10  9:44 sergiodj+buildbot
  2016-10-10  9:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-10  9:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff12a6593a1675aa9ba5340aa2984af19cf8966c ***

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

Remove v850_dbtrap_breakpoint_from_pc

v850 has two functions to install to gdbarch_breakpoint_from_pc,
and it selects one according to info.bfd_arch_info->mach.  However,
we can select the kind/length of breakpoint instruction inside
v850_breakpoint_from_pc by gdbarch_bfd_arch_info (gdbarch)->mach.
This patch is to do that, and remove v850_dbtrap_breakpoint_from_pc.

gdb:

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

	* v850-tdep.c (v850_breakpoint_from_pc): Use the right
	breakpoint instruction.
	(v850_dbtrap_breakpoint_from_pc): Remove.
	(v850_gdbarch_init): Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Rename 'arch' by 'gdbarch' in m32c_gdbarch_init
@ 2016-10-10 10:37 sergiodj+buildbot
  2016-10-10 11:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-10 10:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97ce08cb8071bf9a8df6c99cdf8e9fbf1911f3f5 ***

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

Rename 'arch' by 'gdbarch' in m32c_gdbarch_init

This patch renames local 'arch' by 'gdbarch' in m32c_gdbarch_init, so
that I can use macros in the following patch.

gdb:

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

	* m32c-tdep.c (m32c_gdbarch_init): Rename local 'arch' by
	'gdbarch'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Share enum arm_breakpoint_kinds
@ 2016-10-10 11:41 sergiodj+buildbot
  2016-10-10 12:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-10 11:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a1078bea751d48e8846b91542d91647f1e0aed8d ***

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

Share enum arm_breakpoint_kinds

This patch shares "enum arm_breakpoint_kinds", and use ARM_BP_KIND_THUMB2
in GDB.

gdb:

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

	* arch/arm.h (enum arm_breakpoint_kinds): New.
	* arm-tdep.c (arm_remote_breakpoint_from_pc): Use
	ARM_BP_KIND_THUMB2.

gdb/gdbserver:

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

	* linux-aarch32-low.c (enum arm_breakpoint_kinds): Remove.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Always descend into output section statements in lang_do_assignments
@ 2016-10-11  7:59 sergiodj+buildbot
  2016-10-11  7:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-11  7:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f02cb058822459ea29a9fdaa928c2623df435908 ***

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

Always descend into output section statements in lang_do_assignments

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

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

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] PR target/20666, fix wrong encoding of new introduced BFC pseudo
@ 2016-10-11 10:42 sergiodj+buildbot
  2016-10-11 10:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-11 10:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93562a343c26f67d2bd0e93cceb18a0a793087c2 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 93562a343c26f67d2bd0e93cceb18a0a793087c2

[AArch64] PR target/20666, fix wrong encoding of new introduced BFC pseudo

opcode/
	PR target/20666
	* aarch64-asm.c (convert_bfc_to_bfm): Fix dest index.

gas/
	* testsuite/gas/aarch64/alias-2.d: Update expected results.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Use standard_output_file
@ 2016-10-11 15:00 sergiodj+buildbot
  2016-10-11 15:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-11 15:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16c85b5d14a04c275d3cb39b2029f3dc0f708531 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 16c85b5d14a04c275d3cb39b2029f3dc0f708531

testsuite: Use standard_output_file

gdb/testsuite/ChangeLog
2016-10-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.arch/powerpc-prologue.exp: Use standard_output_file.
	* gdb.arch/ppc64-symtab-cordic.exp: Likewise.
	* gdb.arch/vsx-regs.exp: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] testsuite: Fix gdb.arch/powerpc-prologue.c compilation
@ 2016-10-11 17:27 sergiodj+buildbot
  2016-10-11 17:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-11 17:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f1a8fc4df2244f548d55fbecce20b7cd6f90e16 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 8f1a8fc4df2244f548d55fbecce20b7cd6f90e16

testsuite: Fix gdb.arch/powerpc-prologue.c compilation

gcc-6.2.1

gdb compile failed, gdb/testsuite/gdb.arch/powerpc-prologue.c: In function 'main':
gdb/testsuite/gdb.arch/powerpc-prologue.c:32:3: warning: implicit declaration of function 'optimized_1' [-Wimplicit-function-declaration]
   optimized_1 ();
   ^~~~~~~~~~~

gdb/testsuite/ChangeLog
2016-10-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.arch/powerpc-prologue.c (optimized_1): New declaration.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] BFD_FAKE_SECTION macro params
@ 2016-10-11 23:35 sergiodj+buildbot
  2016-10-11 23:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-11 23:35 UTC (permalink / raw)
  To: gdb-testers

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

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

BFD_FAKE_SECTION macro params

Order NAME, IDX, FLAGS as per STD_SECTION macro.

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Track FP registers in prologue analyzer
@ 2016-10-12 11:51 sergiodj+buildbot
  2016-10-12 11:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-12 11:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 187f5d00acf0ffe5390f282fd4d6285bcd6fccb9 ***

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

[AArch64] Track FP registers in prologue analyzer

We don't track FP registers in aarch64 prologue analyzer, so this causes
an internal error when FP registers are saved by "stp" instruction in
prologue (stp	d8, d9, [sp,#128]),

 tbreak _Unwind_RaiseException^M
 aarch64-tdep.c:335: internal-error: CORE_ADDR aarch64_analyze_prologue(gdbarch*, CORE_ADDR, CORE_ADDR, aarch64_prologue_cache*): Assertion `inst.operands[0].type == AARCH64_OPND_Rt' failed.^M
 A problem internal to GDB has been detected,

This patch teaches GDB to track FP registers (D registers) in prologue
analyzer.

gdb:

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

	PR tdep/20682
	* aarch64-tdep.c: Replace 32 with AARCH64_D_REGISTER_COUNT.
	(aarch64_analyze_prologue): Extend array 'regs' for D registers.
	Assert that operand 0 and 1 can be X or D registers.  Update
	register number for D registers.  Update registers in frame
	cache.
	* aarch64-tdep.h (AARCH64_D_REGISTER_COUNT): New macro.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc: Add a gdbarch_tdep structure
@ 2016-10-12 13:03 sergiodj+buildbot
  2016-10-12 14:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-12 13:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b845c31ecc4fe2677f1d938b0d8a3dc98397158e ***

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

arc: Add a gdbarch_tdep structure

Add target-specific structure gdbarch_tdep for ARC.

gdb/ChangeLog:

	* arc-tdep.h (struct gdbarch_tdep): New.
	* arc-tdep.c (arc_gdbarch_init): Allocate gdbarch_tdep.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc: Add evaluation of long jump targets
@ 2016-10-12 13:32 sergiodj+buildbot
  2016-10-12 15:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-12 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aaf43c4882f827d9f778b40dcdb93566f765f5f9 ***

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

arc: Add evaluation of long jump targets

Standard get_longjmp_target implementation, similar to what is in arm-tdep.c.
Actual value of jb_pc should be set in init_osabi methods of particular OS/ABI
implementations.

gdb/ChangeLog:

	* arc-tdep.h (struct gdbarch_tdep) <jb_pc>: New field.
	* arc-tdep.c (arc_get_longjmp_target): New function.
	(arc_gdbarch_init): Set get_longjmp_target if jb_pc is non-negative.
	(arc_dump_tdep): Print jb_pc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fixup gdb.python/py-value.exp for bare-metal aarch64-elf
@ 2016-10-12 15:51 sergiodj+buildbot
  2016-10-12 18:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-12 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dac951e11030b43b17f52df8bdfa7432e4bf73c ***

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

Fixup gdb.python/py-value.exp for bare-metal aarch64-elf

I noticed that testing aarch64-elf gdb with a physical board
ran into issues with gdb.python/py-value.exp. Further investigation showed
that we were actually trying to dereference a NULL pointer (argv) when trying
to access argv[0].

Being bare-metal, argv is not guaranteed to be valid. So we need to make sure
argv is sane before accessing argv[0].

The following patch fixes up the test program to check for a NULL argv and also
improves the testcase a bit so it doesn't have to work with a hardcoded argc
value.

Regression-tested on x86-64 Ubuntu 16.04.

gdb/testsuite/ChangeLog:

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

	* gdb.python/py-value.c (main): Check if argv is NULL before using it.
	* gdb.python/py-value.exp (test_value_in_inferior): Don't use hardcoded
	argc values.
	Add 1 to argc so we guarantee distinct initial/modified argc values.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc: Add support for Newlib
@ 2016-10-12 16:00 sergiodj+buildbot
  2016-10-12 16:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-12 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a2f4826907de97b089295000a67d2497aa94c99 ***

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

arc: Add support for Newlib

Add support for Newlib as an OS/ABI.  The only thing that is specific to it
relatively to "generic" baremetal target is location of PC register in jump
buffer for longjump support.

Sniffer uses .ivt section to decide if ELF file is for ARC Newlib or not.

gdb/ChangeLog:

	* arc-newlib-tdep.c: New file.
	* configure.tgt: Add newlib support for ARC.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Convert tid_range_parser and get_number_or_range to classes
@ 2016-10-13  1:21 sergiodj+buildbot
  2016-10-13  1:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  1:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfd282882d534cd4f48e2fc29d4ce0923c52352b ***

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

Convert tid_range_parser and get_number_or_range to classes

This converts tid_range_parser and get_number_or_range to be classes.
The various tid_range_parser_* and get_number_or_range_* functions
become methods on the respective classes.  Then it updates the users
to follow.

The rationale for the change is that this provides better
encapsulation.  For example, this forced me to think of a better
interface between tid_range_parser and get_number_or_range, since the
former peeked into the latter's internals a bit too much.  That ended
up resulting mostly in these two not-just-straight-1-1 changes:

  void
 -tid_range_parser_skip (struct tid_range_parser *parser)
 +tid_range_parser::skip_range ()
  {
 ...

 -  tid_range_parser_init (parser, parser->range_parser.end_ptr,
 -			 parser->default_inferior);
 +  m_range_parser.skip_range ();
 +  init (m_range_parser.string (), m_default_inferior);
  }

 and:

    /* If we successfully parsed a thread number or finished parsing a
       thread range, switch back to assuming the next TID is
       inferior-qualified.  */
 -  if (parser->range_parser.end_ptr == NULL
 -      || parser->range_parser.string == parser->range_parser.end_ptr)
 +  if (!m_range_parser.in_range ())
      {

For the same reason (encapsulation), this moves the enum
tid_range_state definition to within the tid_parser class's scope,
since that is private implementation detail.

While at it, switch to use "bool" for booleans.

gdb/ChangeLog:
2016-10-13  Pedro Alves  <palves@redhat.com>
	    Tom Tromey  <tom@tromey.com>

	* tid-parse.h (tid_range_parser): New class.
	(enum tid_range_state): Move into tid_range_parser's scope.
	Remove TID_RANGE_ prefix from all values.
	(tid_range_parser_get_tid, tid_range_parser_get_tid_range)
	(tid_range_parser_star_range, tid_range_parser_finished)
	(tid_range_parser_skip, tid_range_parser_qualified): Don't
	declare.
	(tid_is_in_list): Update comment.
	* tid-parse.c (tid_range_parser::tid_range_parser): New.
	(init, finished, get_string, skip, tid_is_qualified)
	(get_tid_or_range, get_tid_range, get_tid, star_range): Rename;
	turn into methods.
	(tid_is_in_list): Adjust.
	* cli/cli-utils.h (number_or_range_parser): New class.
	(init_number_or_range, get_number_or_range)
	(number_range_setup_range): Don't declare.
	* cli/cli-utils.c
	(number_or_range_parser::number_or_range_parser): New.
	(init_number_or_range, get_number_or_range)
	(number_range_setup_range): Rename; turn into methods.
	(number_is_in_list): Adjust.
	* breakpoint.c (map_breakpoint_numbers): Adjust.  Use bool.
	(trace_pass_command, get_tracepoint_by_number): Adjust.
	* breakpoint.h (get_tracepoint_by_number): Adjust.
	* inferior.c (detach_inferior_command, kill_inferior_command)
	(remove_inferior_command): Adjust.
	* linespec.c (decode_line_2): Adjust.
	* memattr.c (mem_enable_command, mem_disable_command)
	(mem_delete_command): Adjust.
	* printcmd.c (map_display_numbers): Adjust.
	* reverse.c (delete_bookmark_command, bookmarks_info): Adjust.
	* thread.c (thread_apply_command): Adjust.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Change selttest.c to use use std::vector
@ 2016-10-13  2:25 sergiodj+buildbot
  2016-10-13  2:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  2:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 816d7b53047bca81c226990bc9248d59d80d4b8b ***

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

Change selttest.c to use use std::vector

This patch changes selftest.c to use std::vector rather than VEC.
I think this is a small net plus.

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

	* selftest.c: Include <vector>, not "vec.h".
	(self_test_function_ptr): Remove.
	(tests): Now a std::vector.
	(register_self_test, run_self_tests): Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Turn wchar iterator into a class
@ 2016-10-13  2:59 sergiodj+buildbot
  2016-10-13  3:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  2:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cda6c55bd399a8892d62178d4daeb074def909e0 ***

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

Turn wchar iterator into a class

This changes wchar_iterator from charset.c into a real C++ class, then
updates the users to use the class.  This lets us remove some cleanups
in favor of the class' destructor.

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

	* valprint.c (generic_emit_char, count_next_character)
	(generic_printstr): Update.
	* charset.c (struct wchar_iterator): Move to charset.h.
	(wchar_iterator::wchar_iterator): Rename from
	make_wchar_iterator, turn into a constructor.
	(wchar_iterator::~wchar_iterator): Rename from
	do_cleanup_iterator, turn into a destructor.
	(make_cleanup_wchar_iterator): Remove.
	(wchar_iterator::iterate): Rename from wchar_iterate.  Remove
	"iter" argument.  Update.
	* charset.h: Include <vector>.
	(class wchar_iterator): New class, from old struct
	wchar_iterator.
	(make_wchar_iterator, make_cleanup_wchar_iterator): Don't
	declare.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove unnecessary null_cleanup
@ 2016-10-13  4:50 sergiodj+buildbot
  2016-10-13  5:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  4:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1a760cbb796b62f18ff6b81a189fd261809ef74 ***

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

Remove unnecessary null_cleanup

This patch removes an unnecessary null_cleanup.

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

	* tracepoint.c (trace_dump_command): Remove unnecessary
	null_cleanup.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use std::string in macho_symfile_read_all_oso
@ 2016-10-13  5:24 sergiodj+buildbot
  2016-10-13  6:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  5:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af533a5f8b149bfa1394ab04c3947e97dd507a33 ***

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

Use std::string in macho_symfile_read_all_oso

This changes macho_symfile_read_all_oso to use std::string.  This
avoids a cleanup.

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

	* machoread.c (macho_symfile_read_all_oso): Use std::string.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Skip testing structures with floating points
@ 2016-10-13 14:54 sergiodj+buildbot
  2016-10-13 14:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-13 14:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 62df7e210ebf096dc09ad14d9316fcda0f6217f7 ***

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

Skip testing structures with floating points

This patch skips some tests related to floating point in structs.exp
if gdb_skip_float_test return false.

gdb/testsuite:

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

	* gdb.base/structs.exp: Invoke gdb_skip_float_test, and do
	floating point tests if $skip_float_test is false.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Share proc get_var_address
@ 2016-10-13 15:27 sergiodj+buildbot
  2016-10-13 16:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-13 15:27 UTC (permalink / raw)
  To: gdb-testers

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

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

Share proc get_var_address

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

gdb/testsuite:

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] ARI: Remove true/false checks
@ 2016-10-13 17:38 sergiodj+buildbot
  2016-10-13 17:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-13 17:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f2e9c5e3b0ef55cb0ab180dd0c82c7954a73e1a ***

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

ARI: Remove true/false checks

These don't make sense with C++.

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

	* contrib/ari/gdb_ari.sh (boolean): Suggest bool instead.
	(false, true): Remove checks.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Include strings.h where available
@ 2016-10-14  7:30 sergiodj+buildbot
  2016-10-14 17:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-14  7:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ffc1bb12a22e548835c9291871ad0eb68b7f6f0 ***

Author: Eli Zaretskii <eliz@gnu.org>
Branch: master
Commit: 8ffc1bb12a22e548835c9291871ad0eb68b7f6f0

Include strings.h where available

gdb/ChangeLog

2016-10-14  Eli Zaretskii  <eliz@gnu.org>

	* common/common-defs.h [HAVE_STRINGS_H]: Include strings.h if
	available, to get prototypes of 'strcasecmp' and 'strncasecmp'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix set sysroot command on AIX
@ 2016-10-14 13:25 sergiodj+buildbot
  2016-10-15  6:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-14 13:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 754c39c2f32a796ad9983836deb7c4429c808e48 ***

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

Fix set sysroot command on AIX

set sysroot command on AIX has no effect if a program depends on shared
library archives (.a).  Fixed by using solib_find and solib_bfd_fopen
instead of gdb_bfd_open in solib_aix_bfd_open.

gdb/
2016-10-14  Sangamesh Mallayya  <sangamesh.swamy@in.ibm.com>
	    Ulrich Weigand  <uweigand@de.ibm.com>

	* solib-aix.c (solib_aix_bfd_open): Call solib_find so that sysroot
	path is set properly if program has a dependency on .a archive and
	sysroot is set via set sysroot command.

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Move OVERRIDE/FINAL from gcc/coretypes.h to include/ansidecl.h
@ 2016-10-14 16:29 sergiodj+buildbot
  2016-10-15 10:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-14 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d118ee3761bcf0c861a75e454d0c2b741fccb956 ***

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

Move OVERRIDE/FINAL from gcc/coretypes.h to include/ansidecl.h

So that GDB and other projects that share the top level can use them.

Bootstrapped with all default languages + jit on x86-64 Fedora 23.

gcc/ChangeLog:
2016-10-14  Pedro Alves  <palves@redhat.com>

	* coretypes.h (OVERRIDE, FINAL): Delete, moved to
	include/ansidecl.h.

include/ChangeLog:
2016-10-14  Pedro Alves  <palves@redhat.com>

	* ansidecl.h (GCC_FINAL): Delete.
	(OVERRIDE, FINAL): New, moved from gcc/coretypes.h.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Removed pseudo invalid instructions opcodes.
@ 2016-10-17 13:56 sergiodj+buildbot
  2016-10-17 19:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT decf5bd1570be3de10aeab99869a9548d17b1354 ***

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

Removed pseudo invalid instructions opcodes.

The disassember was generating invXXX instructions for cases when in reality we
had llockd or scondd instrutions.

opcodes/ChangeLog:

    Cupertino Miranda  <cmiranda@synopsys.com>
	arc-tbl.h: Removed any "inv.+" instructions from the table.

gas/ChangeLog:

    Cupertino Miranda  <cmiranda@synopsys.com>
        testsuite/arc/dis-inv.s: Test to validate patch.
        testsuite/arc/dis-inv.d: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Fix phony iconv build
@ 2016-10-17 16:34 sergiodj+buildbot
  2016-10-17 22:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5562a44eb490b5777c9e786971907c0727d88495 ***

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

gdb: Fix phony iconv build

Cross building gdb for mingw32 on Fedora 23 fails with:

  x86_64-w64-mingw32-g++ -g -O2  [...]  ../../src/gdb/charset.c
  In file included from ../../src/gdb/charset.c:21:0:
  ../../src/gdb/charset.h:134:3: error: 'iconv_t' does not name a type
     iconv_t m_desc;
     ^
  ../../src/gdb/charset.c: In constructor 'wchar_iterator::wchar_iterator(const gdb_byte*, size_t, const char*, size_t)':
  ../../src/gdb/charset.c:600:3: error: 'm_desc' was not declared in this scope
     m_desc = iconv_open (INTERMEDIATE_ENCODING, charset);
     ^
  ../../src/gdb/charset.c: In destructor 'wchar_iterator::~wchar_iterator()':
  ../../src/gdb/charset.c:607:7: error: 'm_desc' was not declared in this scope
     if (m_desc != (iconv_t) -1)
	 ^
  ../../src/gdb/charset.c: In member function 'int wchar_iterator::iterate(wchar_iterate_result*, gdb_wchar_t**, const gdb_byte**, size_t*)':
  ../../src/gdb/charset.c:633:25: error: 'm_desc' was not declared in this scope
	 size_t r = iconv (m_desc, &inptr, &m_bytes, &outptr, &out_avail);
			   ^

This is a regression caused by commit cda6c55bd399 (Turn wchar
iterator into a class).  The problem is that iconv_t is now exposed in
gdb/charset.h, while before it was only used in gdb/charset.c.

gdb/charset.c, under #ifdef PHONY_ICONV, does:

 #undef iconv_t
 #define iconv_t int

So it seems the simplest is to use 'int' in the header file too.

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

	* charset.h (class wchar_iterator) [PHONY_ICONV] <m_desc>: Use
	'int' as type.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix -trace-save crash when argument is missing
@ 2016-10-17 21:05 sergiodj+buildbot
  2016-10-18  2:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 21:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5bad3170301060ee0801a739ffc213abae664973 ***

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

Fix -trace-save crash when argument is missing

-trace-save doesn't check whether an argument is passed, leading to a
segfault if you pass nothing.

I added a small test, which only tests the error conditions of
-trace-save.

gdb/ChangeLog:

	* mi/mi-main.c (mi_cmd_trace_save): Check if argument is present
	before using it.

gdb/testsuite/ChangeLog:

	* gdb.trace/mi-trace-save.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix duplicate test message in mi-trace-save.exp
@ 2016-10-17 23:24 sergiodj+buildbot
  2016-10-18  9:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 23:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e42b25a0407fbbf3529815f69bd56a61b1821295 ***

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

Fix duplicate test message in mi-trace-save.exp

gdb/testsuite/ChangeLog:

	* gdb.trace/mi-trace-save.exp (test_trace_save_wrong_num_args):
	Change test message.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] ARM/BFD: Correct an `index' global shadowing error
@ 2016-10-25  5:31 sergiodj+buildbot
  2016-10-25 20:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-25  5:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c48182bfe408e06e3301ee887fd9a7b06bedff37 ***

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

ARM/BFD: Correct an `index' global shadowing error

Fix a commit 5025eb7c0d87 ("Delete relocations associatesd with deleted
exidx entries.") build regression:

cc1: warnings being treated as errors
.../bfd/elf32-arm.c: In function 'elf32_arm_update_relocs':
.../bfd/elf32-arm.c:14951: warning: declaration of 'index' shadows a global declaration
/usr/include/string.h:304: warning: shadowed declaration is here
make[3]: *** [elf32-arm.lo] Error 1

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

	bfd/
	* elf32-arm.c (elf32_arm_update_relocs): Rename `index' local
	variable to `reloc_index'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Clean up remote.c:remote_resume
@ 2016-10-26 16:05 sergiodj+buildbot
  2016-10-26 18:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 16:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b68ffbb32645c5383e74f27248a1c1c7ecd241a ***

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

gdb: Clean up remote.c:remote_resume

Just some refactoring / TLC.  Mainly split the old c/s/C/S packet
handling to a separate function.

gdb/ChangeLog:
2016-10-26  Pedro Alves  <palves@redhat.com>

	* remote.c (remote_resume_with_hc): New function, factored out
	from ...
	(remote_resume): ... this.  Always try vCont first.
	(remote_vcont_resume): Rename to ...
	(remote_resume_with_vcont): ... this.  Bail out if execution
	direction is reverse.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Free inferior->priv when inferior exits
@ 2016-10-26 20:33 sergiodj+buildbot
  2016-11-04 22:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 20:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef4a339527a41802fbab70af25d6e4788f35dcc8 ***

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

gdb: Free inferior->priv when inferior exits

(Where "exits" includes being killed or detached.)

Nothing is clearing inferior->priv currently.  This is a problem if we
change the inferior's process_stratum targets in a single debug
session.  This field is currently only used by darwin-nat.c, but a
follow up patch will make remote.c use it too.  Without the fix,
remote.c might end up mistaking the priv object allocated by
darwin-nat.c with its own.

(Found by inspection.)

gdb/ChangeLog:
2016-10-26  Pedro Alves  <palves@redhat.com>

	* inferior.c (exit_inferior_1): Free 'priv'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for RISC-V architecture.
@ 2016-11-01 17:00 sergiodj+buildbot
  2016-11-08 23:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-01 17:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e23eba971dd409b999dd83d8df0f842680c1c642 ***

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

Add support for RISC-V architecture.

bfd	* Makefile.am: Add entries for riscv32-elf and riscv64-elf.
	* config.bdf: Likewise.
	* configure.ac: Likewise.
	* Makefile.in: Regenerate.
	* configure: Regenerate.
	* archures.c: Add bfd_riscv_arch.
	* reloc.c: Add riscv relocs.
	* targets.c: Add riscv_elf32_vec and riscv_elf64_vec.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
	* elf-bfd.h: Add RISCV_ELF_DATA to enum elf_target_id.
	* elfnn-riscv.c: New file.
	* elfxx-riscv.c: New file.
	* elfxx-riscv.h: New file.

binutils* readelf.c (guess_is_rela): Add EM_RISCV.
	(get_machine_name): Likewise.
	(dump_relocations): Add support for riscv relocations.
	(get_machine_flags): Add support for riscv flags.
	(is_32bit_abs_reloc): Add R_RISCV_32.
	(is_64bit_abs_reloc): Add R_RISCV_64.
	(is_none_reloc): Add R_RISCV_NONE.
	* testsuite/binutils-all/objdump.exp (cpus_expected): Add riscv.
	Expect the debug_ranges test to fail.

gas	* Makefile.am: Add riscv files.
	* Makefile.in: Regenerate.
	* NEWS: Mention the support for this architecture.
	* configure.in: Define a default architecture.
	* configure: Regenerate.
	* configure.tgt: Add entries for riscv.
	* doc/as.texinfo: Likewise.
	* testsuite/gas/all/gas.exp: Expect the redef tests to fail.
	* testsuite/gas/elf/elf.exp: Expect the groupauto tests to fail.
	* config/tc-riscv.c: New file.
	* config/tc-riscv.h: New file.
	* doc/c-riscv.texi: New file.
	* testsuite/gas/riscv: New directory.
	* testsuite/gas/riscv/riscv.exp: New file.
	* testsuite/gas/riscv/t_insns.d: New file.
	* testsuite/gas/riscv/t_insns.s: New file.

ld	* Makefile.am: Add riscv files.
	* Makefile.in: Regenerate.
	* NEWS: Mention the support for this target.
	* configure.tgt: Add riscv entries.
	* emulparams/elf32lriscv-defs.sh: New file.
	* emulparams/elf32lriscv.sh: New file.
	* emulparams/elf64lriscv-defs.sh: New file.
	* emulparams/elf64lriscv.sh: New file.
	* emultempl/riscvelf.em: New file.

opcodes	* configure.ac: Add entry for bfd_riscv_arch.
	* configure: Regenerate.
	* disassemble.c (disassembler): Add support for riscv.
	(disassembler_usage): Likewise.
	* riscv-dis.c: New file.
	* riscv-opc.c: New file.

include	* dis-asm.h: Add prototypes for print_insn_riscv and
	print_riscv_disassembler_options.
	* elf/riscv.h: New file.
	* opcode/riscv-opc.h: New file.
	* opcode/riscv.h: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] GDBARCH_BREAKPOINT_MANIPULATION and SET_GDBARCH_BREAKPOINT_MANIPULATION
@ 2016-11-03 15:14 sergiodj+buildbot
  2016-11-10  2:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 15:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 598cc9dc84aeaa66e4a77efa9dc8ff03d5532620 ***

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

GDBARCH_BREAKPOINT_MANIPULATION and SET_GDBARCH_BREAKPOINT_MANIPULATION

Many archs have only one kind of breakpoint, so their breakpoint_from_pc
implementations are quite similar.  This patch uses macro
GDBARCH_BREAKPOINT_MANIPULATION and SET_GDBARCH_BREAKPOINT_MANIPULATION
for breakpoint_from_pc, so that we can easily switch from
breakpoint_from_pc to breakpoint_kind_from_pc and sw_breakpoint_from_kind
later.

gdb:

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

	* arch-utils.h (GDBARCH_BREAKPOINT_MANIPULATION): New macro.
	(SET_GDBARCH_BREAKPOINT_MANIPULATION): New macro.
	aarch64-tdep.c (aarch64_breakpoint_from_pc): Remove.  Use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(aarch64_gdbarch_init): Replace set_gdbarch_breakpoint_from_pc
	with SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* alpha-tdep.c: Likewise.
	* avr-tdep.c: Likewise.
	* frv-tdep.c: Likewise.
	* ft32-tdep.c: Likewise.
	* h8300-tdep.c: Likewise.
	* hppa-tdep.c: Likewise.
	* i386-tdep.c: Likewise.
	* lm32-tdep.c: Likewise.
	* m32c-tdep.c: Likewise.
	* m68hc11-tdep.c: Likewise.
	* m68k-tdep.c: Likewise.
	* m88k-tdep.c: Likewise.
	* mep-tdep.c: Likewise.
	* microblaze-tdep.c: Likewise.
	* mn10300-tdep.c: Likewise.
	* moxie-tdep.c: Likewise.
	* msp430-tdep.c: Likewise.
	* rl78-tdep.c: Likewise.
	* rx-tdep.c: Likewise.
	* s390-linux-tdep.c: Likewise.
	* sparc-tdep.c: Likewise.
	* spu-tdep.c: Likewise.
	* tilegx-tdep.c: Likewise.
	* vax-tdep.c: Likewise.
	* xstormy16-tdep.c: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] New gdbarch methods breakpoint_kind_from_pc and sw_breakpoint_from_kind
@ 2016-11-03 15:40 sergiodj+buildbot
  2016-11-10 13:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 15:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd6c3b4ffc4ea6f56f12581419e2eed885441beb ***

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

New gdbarch methods breakpoint_kind_from_pc and sw_breakpoint_from_kind

This patch adds two gdbarch methods breakpoint_kind_from_pc and
sw_breakpoint_from_kind, and uses target_info.placed_size as "kind"
of the breakpoint.  This patch updates the usages of
target_info.placed_size.

The "kind" of a breakpoint is determined by gdbarch rather than
target, so we have gdbarch method breakpoint_kind_from_pc, and we
should set target_info.placed_size out of each implementation of
target to_insert_breakpoint.  In this way, each target doesn't have
to set target_info.placed_size any more.

This patch also sets target_info.placed_address before
target_insert_breakpoint too, so that target to_insert_breakpoint
can use it, see record_full_insert_breakpoint.

Before we call target_insert_breakpoint, we set
target_info.placed_address and target_info.placed_size like this,

      CORE_ADDR addr = bl->target_info.reqstd_address;

      bl->target_info.placed_size = gdbarch_breakpoint_kind_from_pc (bl->gdbarch, &addr);
      bl->target_info.placed_address = addr;

      return target_insert_breakpoint (bl->gdbarch, &bl->target_info);

target_insert_breakpoint may fail, but it doesn't matter to the "kind"
and "placed_address" of a breakpoint.  They should be determined by
gdbarch.

gdb:

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

	* arch-utils.h (GDBARCH_BREAKPOINT_MANIPULATION): Define
	breakpoint_kind_from_pc and sw_breakpoint_from_kind.
	(GDBARCH_BREAKPOINT_MANIPULATION_ENDIAN): Likewise.
	(SET_GDBARCH_BREAKPOINT_MANIPULATION): Call
	set_gdbarch_breakpoint_kind_from_pc and
	set_gdbarch_sw_breakpoint_from_kind.
	* arm-tdep.c: Add comments.
	* bfin-tdep.c: Likewise.
	* breakpoint.c (breakpoint_kind): New function.
	(insert_bp_location): Set target_info.placed_size and
	target_info.placed_address.
	(bkpt_insert_location): Likewise.
	* cris-tdep.c: Add comments.
	* gdbarch.sh (breakpoint_kind_from_pc): New.
	(sw_breakpoint_from_kind): New.
	* gdbarch.c, gdbarch.h: Regenerated.
	* ia64-tdep.c (ia64_memory_insert_breakpoint): Don't set
	bp_tgt->placed_size.
	(ia64_memory_remove_breakpoint): Don't assert
	bp_tgt->placed_size.
	(ia64_breakpoint_kind_from_pc): New function.
	(ia64_gdbarch_init): Install ia64_breakpoint_kind_from_pc.
	* m32r-tdep.c (m32r_memory_insert_breakpoint): Don't set
	bp_tgt->placed_size.
	* mem-break.c (default_memory_insert_breakpoint): Don't set
	bp_tgt->placed_size.  Call gdbarch_sw_breakpoint_from_kind.
	(default_memory_remove_breakpoint): Call
	gdbarch_sw_breakpoint_from_kind.
	(memory_validate_breakpoint): Don't check bp_tgt->placed_size.
	* mips-tdep.c: Add comments.
	* mt-tdep.c: Likewise.
	* nios2-tdep.c: Likewise.
	* record-full.c (record_full_insert_breakpoint): Don't call
	gdbarch_breakpoint_from_pc.  Don't set bp_tgt->placed_address
	and bp_tgt->placed_size.
	* remote.c (remote_insert_breakpoint): Don't call
	gdbarch_remote_breakpoint_from_pc.  Use bp_tgt->placed_size.
	Don't set bp_tgt->placed_address and bp_tgt->placed_size.
	(remote_insert_hw_breakpoint): Likewise.
	* score-tdep.c: Likewise.
	* sh-tdep.c: Likewise.
	* tic6x-tdep.c: Likewise.
	* v850-tdep.c: Likewise.
	* xtensa-tdep.c: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Rename placed_size to kind
@ 2016-11-03 15:46 sergiodj+buildbot
  2016-11-10 13:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 15:46 UTC (permalink / raw)
  To: gdb-testers

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

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

Rename placed_size to kind

This patch renames placed_size to kind.

gdb:

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove gdbarch_remote_breakpoint_from_pc
@ 2016-11-03 15:50 sergiodj+buildbot
  2016-11-10 13:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0f4a997c26760d2584946196ee5c411d1a632a6 ***

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

Remove gdbarch_remote_breakpoint_from_pc

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

gdb:

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add default_breakpoint_from_pc
@ 2016-11-03 16:05 sergiodj+buildbot
  2016-11-10 13:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 16:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22f13eb869197fc45a0da2a8a96b03d39809862e ***

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

Add default_breakpoint_from_pc

This patch adds the default implementation of gdbarch breakpoint_from_pc,
which is,

const gdb_byte *
default_breakpoint_from_pc (struct gdbarch *gdbarch, CORE_ADDR *pcptr,
                           int *lenptr)
{
  int kind = gdbarch_breakpoint_kind_from_pc (gdbarch, pcptr);

  return gdbarch_sw_breakpoint_from_kind (gdbarch, kind, lenptr);
}

so gdbarch can only defines sw_breakpoint_from_kind and
breakpoint_kind_from_pc.

gdb:

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

	* arch-utils.c (default_breakpoint_from_pc): New function.
	* arch-utils.h (GDBARCH_BREAKPOINT_FROM_PC): Remove.
	(GDBARCH_BREAKPOINT_MANIPULATION): Don't use
	GDBARCH_BREAKPOINT_FROM_PC.
	(SET_GDBARCH_BREAKPOINT_MANIPULATION): Don't call
	set_gdbarch_breakpoint_from_pc.
	(default_breakpoint_from_pc): Remove declaration.
	* gdbarch.sh (breakpoint_from_pc): Add its default implementation.
	* gdbarch.c, gdbarch.h: Regenerate.
	* arm-tdep.c: Don't use GDBARCH_BREAKPOINT_FROM_PC.
	* arc-tdep.c, bfin-tdep.c, cris-tdep.c, iq2000-tdep.c: Likewise.
	* m32r-tdep.c, mips-tdep.c, mt-tdep.c: Likewise.
	* nios2-tdep.c, score-tdep.c, sh-tdep.c: Likewise.
	* sh64-tdep.c, tic6x-tdep.c, v850-tdep.c, xtensa-tdep.c: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Determine the kind of single step breakpoint
@ 2016-11-03 16:16 sergiodj+buildbot
  2016-11-10 13:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 16:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 833b7ab5008b769dca6db6d5ee1d21d33e730132 ***

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

Determine the kind of single step breakpoint

This patch adds a new gdbarch method breakpoint_kind_from_current_state
for single step breakpoint, and uses it in breakpoint_kind.

gdb:

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

	* arch-utils.c (default_breakpoint_kind_from_current_state):
	New function.
	* arch-utils.h (default_breakpoint_kind_from_current_state):
	Declare.
	* arm-tdep.c (arm_breakpoint_kind_from_current_state): New
	function.
	(arm_gdbarch_init): Call
	set_gdbarch_breakpoint_kind_from_current_state.
	* breakpoint.c (breakpoint_kind): Call
	gdbarch_breakpoint_kind_from_current_state for single step
	breakpoint.  Update comments.
	* gdbarch.sh (breakpoint_kind_from_current_state): New.
	* gdbarch.c, gdbarch.h: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove arm_override_mode
@ 2016-11-03 16:26 sergiodj+buildbot
  2016-11-10 13:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 16:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a97c97e8d7c818886f0f7beb3fd5dee0042b4a07 ***

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

Remove arm_override_mode

GDB can determine the kind of single step breakpoint by gdbarch
breakpoint_kind_from_current_state, so global variable
arm_override_mode is no longer needed.  This patch removes it.

gdb:

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

	* arm-tdep.c (arm_override_mode): Remove.
	(arm_pc_is_thumb): Update.
	(arm_insert_single_step_breakpoint): Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove GDBARCH_BREAKPOINT_MANIPULATION and SET_GDBARCH_BREAKPOINT_MANIPULATION
@ 2016-11-03 16:27 sergiodj+buildbot
  2016-11-10 13:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 16:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04180708eff91ddd3a9572bd4b517ccce5850db0 ***

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

Remove GDBARCH_BREAKPOINT_MANIPULATION and SET_GDBARCH_BREAKPOINT_MANIPULATION

Both of them are used in conversion.  We can remove them since the
conversion is done.

There are many architectures only have one breakpoint instruction,
so their gdbarch methods breakpoint_kind_from_pc and
sw_breakpoint_from_kind look very similar.  Instead of macro, we
use template "template <size_t, const gdb_byte *> struct bp_manipulation"
for these architectures.  In order to use template, I also change
breakpoint instruction of type "static const gdb_byte[]" to
"constexpr gdb_byte[]", and rename them to ARCH_break_insn.

gdb:

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

	* aarch64-tdep.c (aarch64_default_breakpoint): Change it to
	constexpr.  Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(aarch64_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* alpha-tdep.c (break_insn): Rename to alpha_break_insn.
	Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(alpha_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* arc-tdep.c (arc_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* arch-utils.h (GDBARCH_BREAKPOINT_MANIPULATION): Remove.
	(struct bp_manipulation): New.
	(SET_GDBARCH_BREAKPOINT_MANIPULATION): Remove.
	(struct bp_manipulation_endian): New.
	(BP_MANIPULATION): New.
	(BP_MANIPULATION_ENDIAN): New.
	* arm-tdep.c (arm_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* avr-tdep.c (avr_break_insn): Change it constexpr.
	(avr_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* bfin-tdep.c (bfin_gdbarch_init): Likewise.
	* cris-tdep.c (cris_gdbarch_init): Likewise.
	* frv-tdep.c (breakpoint): Rename it to frv_break_insn, and
	change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(frv_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* ft32-tdep.c (breakpoint): Rename it to ft32_break_insn and
	change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(ft32_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* h8300-tdep.c (breakpoint): Rename it to h8300_break_insn.
	Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(h8300_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* hppa-tdep.c (breakpoint): Rename it to h8300_break_insn.
	Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(hppa_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* i386-tdep.c (break_insn): Rename it to i386_break_insn.
	Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(i386_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* iq2000-tdep.c (iq2000_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* lm32-tdep.c (breakpoint): Rename it to lm32_break_insn and
	change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(lm32_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* m32c-tdep.c (break_insn): Rename it to m32c_break_insn and change
	its type to constexpr.  Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(m32c_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* m32r-tdep.c (m32r_gdbarch_init): Likewise.
	* m68hc11-tdep.c (breakpoint): Rename it to m68hc11_break_insn and
	change its type to constexpr.  Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(m68hc11_gdbarch_init): Don't use SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* m68k-tdep.c (break_insn): Rename it to m68k_break_insn and change
	its type to constexpr.  Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(m68k_gdbarch_init):  Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* m88k-tdep.c (break_insn): Rename it to m88k_break_insn and change
	its type to constexpr.  Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(m88k_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* mep-tdep.c (breakpoint): Rename it to mep_break_insn and change
	its type to constexpr.  Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(mep_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* microblaze-tdep.c (break_insn): Rename it to
	microblaze_break_insn and change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(microblaze_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* mips-tdep.c (mips_gdbarch_init): Likewise.
	* mn10300-tdep.c (breakpoint): Rename it to mn10300_break_insn and
	change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(mn10300_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* moxie-tdep.c (breakpoint): Rename it to moxie_break_insn and
	change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(moxie_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* msp430-tdep.c (breakpoint): Rename it to msp430_break_insn
	and change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(msp430_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* mt-tdep.c (mt_gdbarch_init): Likewise.
	* nds32-tdep.c (break_insn): Rename it to nds32_break_insn
	and change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(nds32_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* nios2-tdep.c (nios2_gdbarch_init): Likewise.
	* rl78-tdep.c (breakpoint): Rename it to rl78_break_ins
	and change its type to rl78_break_insn.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(rl78_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* rs6000-tdep.c (big_breakpoint): Change its type to
	constexpr.
	(little_breakpoint): Likewise.
	Don't use GDBARCH_BREAKPOINT_MANIPULATION_ENDIAN.
	(rs6000_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* rx-tdep.c (breakpoint): Rename it to rx_break_insn and
	change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(rx_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* s390-linux-tdep.c (breakpoint): Rename it to s390_break_insn
	and change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION
	(s390_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* score-tdep.c (score_gdbarch_init): Likewise.
	* sh-tdep.c (sh_gdbarch_init): Likewise.
	* sh64-tdep.c (sh64_gdbarch_init): Likewise.
	* sparc-tdep.c (break_insn): Rename it to sparc_break_insn
	and change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(sparc32_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* spu-tdep.c (breakpoint): Rename it to spu_break_insn and change
	its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(spu_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* tic6x-tdep.c (tic6x_gdbarch_init): Likewise.
	* tilegx-tdep.c (breakpoint): Rename it to tilegx_break_insn
	and change its type to constexpr.  Don't use
	GDBARCH_BREAKPOINT_MANIPULATION.
	(tilegx_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* v850-tdep.c (v850_gdbarch_init): Likewise.
	* vax-tdep.c (break_insn): Rename it to vax_break_insn and
	change its type to constexpr.
	Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(vax_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* xstormy16-tdep.c (breakpoint): Rename it to
	xstormy16_break_insn and change its type to constexpr.
	Don't use GDBARCH_BREAKPOINT_MANIPULATION.
	(xstormy16_gdbarch_init): Don't use
	SET_GDBARCH_BREAKPOINT_MANIPULATION.
	* xtensa-tdep.c (xtensa_gdbarch_init): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] X86: Rename REG_82 to REG_83
@ 2016-11-03 16:43 sergiodj+buildbot
  2016-11-10 13:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 16:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7148c36989ee64f15ac9618543309cd7311b6015 ***

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

X86: Rename REG_82 to REG_83

The REG_82 entry in x86 disassembler is for opcode 0x83, not opcode
0x82.

	* i386-dis.c (REG_82): Renamed to ...
	(REG_83): This.
	(dis386): Updated.
	(reg_table): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Deprecate old platforms
@ 2016-11-03 16:59 sergiodj+buildbot
  2016-11-10 13:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 16:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 034b77cf7875c4ea5aaf3d06dfea2e422abc47db ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: 034b77cf7875c4ea5aaf3d06dfea2e422abc47db

Deprecate old platforms

bfd/
	* config.bfd: Deprecate many old triplets.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Replace YY_NULL with YY_NULLPTR in LANG-exp.c
@ 2016-11-03 17:04 sergiodj+buildbot
  2016-11-10 13:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 722bcb33bf0383487c1af0e7d401e30301e94e2b ***

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

Replace YY_NULL with YY_NULLPTR in LANG-exp.c

As we require c++11, GDB fails to build if bison is not new enough.
I see the following error on the system (fedora 19) that bison is
2.6.4,

g++ -std=gnu++11 .... \
	-c -o ada-exp.o -MT ada-exp.o -MMD -MP -MF .deps/ada-exp.Tpo 'if test -f ada-exp.c; then echo ada-exp.c; else echo ../../binutils-gdb/gdb/ada-exp.c; fi`
In file included from ../../binutils-gdb/gdb/ada-exp.y:731:0:
ada-lex.c:113:0: error: "YY_NULL" redefined [-Werror]
 #define YY_NULL 0
 ^
ada-exp.c:158:0: note: this is the location of the previous definition
 #   define YY_NULL nullptr
 ^
cc1plus: all warnings being treated as errors
make: *** [ada-exp.o] Error 1

Both ada-exp.c and ada-lex.c has macro YY_NULL, like this,

 $ cat 1.c
 # ifndef YY_NULL
 #  if defined __cplusplus && 201103L <= __cplusplus
 #   define YY_NULL nullptr
 #  else
 #   define YY_NULL 0
 #  endif
 # endif

 #define YY_NULL 0

as we can see, YY_NULL is defined differently (nullptr vs 0)

$ g++ -std=c++11 -Wall 1.c -c
1.c:9:0: warning: "YY_NULL" redefined
 #define YY_NULL 0
 ^
1.c:3:0: note: this is the location of the previous definition
 #   define YY_NULL nullptr
 ^
$ g++ -Wall 1.c -c

bison renames YY_NULL to YY_NULLPTR in 2013 Nov,
https://lists.gnu.org/archive/html/bison-patches/2013-11/msg00002.html
and bison released later than 2013 Nov have this patch.  Bison 3.0.2,
released on 2013 Dec, is OK.

The fix is to replace YY_NULL with YY_NULLPTR via sed.  With old bison,
YY_NULL becomes YY_NULLPTR; with new bison, YY_NULLPTR becomes
YY_NULLPTRPTR,

gdb:

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

	* Makefile.in (.y.c): Replace YY_NULL with YY_NULLPTR.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] X86: Decode opcode 0x82 as opcode 0x80 in 32-bit mode
@ 2016-11-03 17:21 sergiodj+buildbot
  2016-11-10 13:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 17:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b89fe14b522cd6e5d160ff17defa8ecec243b11 ***

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

X86: Decode opcode 0x82 as opcode 0x80 in 32-bit mode

Update x86 disassembler to treat opcode 0x82 as an aliase of opcode 0x80
in 32-bit mode.

gas/

	PR binutils/20754
	* testsuite/gas/i386/opcode.s: Add tests for opcode 0x82.
	* testsuite/gas/i386/opcode-intel.d: Updated.
	* testsuite/gas/i386/opcode.d: Likewise.

opcodes/

	PR binutils/20754
	* i386-dis.c (REG_82): New.
	(X86_64_82_REG_0): Likewise.
	(X86_64_82_REG_1): Likewise.
	(X86_64_82_REG_2): Likewise.
	(X86_64_82_REG_3): Likewise.
	(X86_64_82_REG_4): Likewise.
	(X86_64_82_REG_5): Likewise.
	(X86_64_82_REG_6): Likewise.
	(X86_64_82_REG_7): Likewise.
	(dis386): Use REG_82.
	(reg_table): Add REG_82.
	(x86_64_table): Add X86_64_82_REG_0, X86_64_82_REG_1,
	X86_64_82_REG_2, X86_64_82_REG_3, X86_64_82_REG_4,
	X86_64_82_REG_5, X86_64_82_REG_6 and X86_64_82_REG_7.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] X86: Reuse opcode 0x80 decoder for opcode 0x82
@ 2016-11-03 17:33 sergiodj+buildbot
  2016-11-10 13:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 17:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d039fef395c1b5fd781acaf1c611f96f654f5f91 ***

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

X86: Reuse opcode 0x80 decoder for opcode 0x82

Since opcode 0x82 is an alias of opcode 0x80, we can reuse opcode 0x80
decoder.

	* i386-dis.c (REG_82): Removed.
	(X86_64_82_REG_0): Likewise.
	(X86_64_82_REG_1): Likewise.
	(X86_64_82_REG_2): Likewise.
	(X86_64_82_REG_3): Likewise.
	(X86_64_82_REG_4): Likewise.
	(X86_64_82_REG_5): Likewise.
	(X86_64_82_REG_6): Likewise.
	(X86_64_82_REG_7): Likewise.
	(X86_64_82): New.
	(dis386): Use X86_64_82 instead of REG_82.
	(reg_table): Remove REG_82.
	(x86_64_table): Add X86_64_82.  Remove X86_64_82_REG_0,
	X86_64_82_REG_1, X86_64_82_REG_2, X86_64_82_REG_3,
	X86_64_82_REG_4, X86_64_82_REG_5, X86_64_82_REG_6 and
	X86_64_82_REG_7.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc/opcodes/nps400: Fix some instruction masks
@ 2016-11-03 17:39 sergiodj+buildbot
  2016-11-10 13:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ecf64ec654afe916099f0fe482c2dae417913905 ***

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

arc/opcodes/nps400: Fix some instruction masks

A few masks were incorrect, there were opcode bits that lives outside of
the instruction mask, the effected instructions are decode1, zncv, and
efabgt.

Previously these instructions would assemble and disassemble correctly,
and a correctly encoded binary should behave no differently.  The only
difference would be seen in a few incorrectly encoded binaries,
previously these would have decoded to the above instructions, while now
they will not.

opcodes/ChangeLog:

	* arc-nps400-tbl.h: Fix some instruction masks.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc: Replace ARC_SHORT macro with arc_opcode_len function
@ 2016-11-03 17:51 sergiodj+buildbot
  2016-11-10 13:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 17:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 06fe285fd293e999481ec8f5c619658aa5e3b48b ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 06fe285fd293e999481ec8f5c619658aa5e3b48b

arc: Replace ARC_SHORT macro with arc_opcode_len function

In preparation for moving to a world where arc instructions can be 2, 4,
6, or 8 bytes in length, replace the ARC_SHORT macro (which is either
true of false) with an arc_opcode_len function that returns a length in
bytes.

There should be no functional change after this commit.

gas/ChangeLog:

	* config/tc-arc.c (assemble_insn): Replace use of ARC_SHORT with
	arc_opcode_len.

include/ChangeLog:

	* opcode/arc.h (arc_opcode_len): Declare.
	(ARC_SHORT): Delete.

opcodes/ChangeLog:

	* arc-dis.c (find_format_from_table): Replace use of ARC_SHORT
	with arc_opcode_len.
	(find_format_long_instructions): Likewise.
	* arc-opc.c (arc_opcode_len): New function.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] opcodes/arc: Make some macros 64-bit safe
@ 2016-11-03 18:03 sergiodj+buildbot
  2016-11-10 13:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 18:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e27220211249bfeb38b10e630b33fbd170fce6c ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 2e27220211249bfeb38b10e630b33fbd170fce6c

opcodes/arc: Make some macros 64-bit safe

In preparation to moving to a world where arc instructions can be 2, 4,
6, or 8 bytes long, make some macros 64-bit safe.

There should be no functional change after this commit.

include/ChangeLog:

	* opcode/arc.h: Make macros 64-bit safe.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc: Swap highbyte and lowbyte in print_insn_arc
@ 2016-11-03 18:15 sergiodj+buildbot
  2016-11-10 13:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 18:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 90f61cceac73fe40dcd21b3590c247bfa624ac00 ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 90f61cceac73fe40dcd21b3590c247bfa624ac00

arc: Swap highbyte and lowbyte in print_insn_arc

highbyte and lowbyte actually refer to the low byte and the high
byte respectively, but are used consistently in this swapped
order. This commit swaps them round so that highbyte refers to the
high byte and lowbyte refers to the low byte.

There should be no functional change after this commit.

opcodes/ChangeLog:

   * arc-dis.c (print_insn_arc): Swap highbyte and lowbyte.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc: Change max instruction length to 64-bits
@ 2016-11-03 18:26 sergiodj+buildbot
  2016-11-10 13:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 18:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdfe53e3cfebb392b1a0ef50fdd02faafec6dc63 ***

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

arc: Change max instruction length to 64-bits

The current handling for arc instructions longer than 32-bits is all
handled as a special case in both the assembler and disassembler.

The problem with this approach is that it leads to code duplication,
selecting a long instruction is exactly the same process as selecting a
short instruction, except over more bits, in both cases we select based
on bit comparison, and initial operand insertion and extraction.

This commit unifies both the long and short instruction worlds,
converting the core opcodes library from being largely 32-bit focused,
to being largely 64-bit focused.

The changes are, on the whole, not too much.  There's obviously a lot of
type changes but otherwise the bulk of the code just works.  Most of the
actual functional changes are to code that previously handled the longer
48 or 64 bit instructions.  The insert/extract handlers for these have
now been brought into line with the short instruction insert/extract
handlers.

All of the special case handling code that was previously added has now
been removed again.  Overall, this commit reduces the amount of code in
the arc assembler and disassembler.

gas/ChangeLog:

	* config/tc-arc.c (struct arc_insn): Change type of insn field.
	(md_number_to_chars_midend): Support 6- and 8-byte values.
	(emit_insn0): Update debug output.
	(find_opcode_match): Likewise.
	(build_fake_opcode_hash_entry): Delete.
	(find_special_case_long_opcode): Delete.
	(find_special_case): Remove long format special case handling.
	(insert_operand): Change instruction type and update debug print
	format.
	(assemble_insn): Change instruction type, update debug print
	formats, and remove unneeded assert.

include/ChangeLog:

	* opcode/arc.h (struct arc_opcode): Change type of opcode and mask
	fields.
	(struct arc_long_opcode): Delete.
	(struct arc_operand): Change types for insert and extract
	handlers.

opcodes/ChangeLog:

	* arc-dis.c (struct arc_operand_iterator): Remove all fields
	relating to long instruction processing, add new limm field.
	(OPCODE): Rename to...
	(OPCODE_32BIT_INSN): ...this.
	(OPCODE_AC): Delete.
	(skip_this_opcode): Handle different instruction lengths, update
	macro name.
	(special_flag_p): Update parameter type.
	(find_format_from_table): Update for more instruction lengths.
	(find_format_long_instructions): Delete.
	(find_format): Update for more instruction lengths.
	(arc_insn_length): Likewise.
	(extract_operand_value): Update for more instruction lengths.
	(operand_iterator_next): Remove code relating to long
	instructions.
	(arc_opcode_to_insn_type): New function.
	(print_insn_arc):Update for more instructions lengths.
	* arc-ext.c (extInstruction_t): Change argument type.
	* arc-ext.h (extInstruction_t): Change argument type.
	* arc-fxi.h: Change type unsigned to unsigned long long
	extensively throughout.
	* arc-nps400-tbl.h: Add long instructions taken from
	arc_long_opcodes table in arc-opc.c.
	* arc-opc.c: Update parameter types on insert/extract handlers.
	(arc_long_opcodes): Delete.
	(arc_num_long_opcodes): Delete.
	(arc_opcode_len): Update for more instruction lengths.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc: Implement NPS-400 dcmac instruction
@ 2016-11-03 18:59 sergiodj+buildbot
  2016-11-10 13:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 18:59 UTC (permalink / raw)
  To: gdb-testers

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

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

arc: Implement NPS-400 dcmac instruction

gas/ChangeLog:

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

include/ChangeLog:

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

opcodes/ChangeLog:

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix handling of discriminantless univariant enums in Rust; fix bug with encoded enums
@ 2016-11-03 23:05 sergiodj+buildbot
  2016-11-10 13:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 23:05 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for untagged unions in Rust
@ 2016-11-03 23:17 sergiodj+buildbot
  2016-11-10 13:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 23:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b96645f1a1e6084ed6a20ddf615bdc4d2487a9c9 ***

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

Add support for untagged unions in Rust

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

gdb/ChangeLog:
    * rust-lang.c (rust_union_is_untagged): Add function to
    check if a union is an untagged unioni
    (rust_val_print): Handle printing of untagged union values
    (rust_print_type): Handle printing of untagged union types
    (rust_evaluate_subexp): Handle evaluating field
    access on untagged unions


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for the sizeof function in Rust
@ 2016-11-03 23:26 sergiodj+buildbot
  2016-11-10 13:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 23:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cdf5a07c75b47481da1e99ee91ee860c2a6bb5f6 ***

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

Add support for the sizeof function in Rust

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

gdb/ChangeLog:
    * rust-exp.y: Parse `sizeof(exp)` as `UNOP_SIZEOF`

gdb/testsuite/ChangeLog:
    * gdb.rust/simple.exp: Add tests for `sizeof(expr)`


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix building binutils for all 32-bit targets by moving riscv32 target into 64-bit builds only.
@ 2016-11-04 14:52 sergiodj+buildbot
  2016-11-10 13:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-04 14:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b7a12f2d68f2f334fbe78cc2db76982ba6d4ef1 ***

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

Fix building binutils for all 32-bit targets by moving riscv32 target into 64-bit builds only.

	* targets.c (bfd_target_vector): Only add riscv_elf32_vec target
	when supporting 64-bit BFD targets.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for ARM Cortex-M33 processor
@ 2016-11-04 17:12 sergiodj+buildbot
  2016-11-10 13:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-04 17:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b19ea8d28b1c06c2973738c1cda076f895ac3ad0 ***

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

Add support for ARM Cortex-M33 processor

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

gas/
	* config/tc-arm.c (cortex-m33): Declare new processor.
	* doc/c-arm.texi (-mcpu ARM command line option): Document new
	Cortex-M33 processor.
	* NEWS: Mention ARM Cortex-M33 support.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc/nps400: Validate address type operands correctly
@ 2016-11-04 23:14 sergiodj+buildbot
  2016-11-10 13:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-04 23:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b437d035ddf4e4c0c566c577ee059790ed28ad9b ***

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

arc/nps400: Validate address type operands correctly

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

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

gas/ChangeLog:

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

opcodes/ChangeLog:

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix a few typos
@ 2016-11-05  4:41 sergiodj+buildbot
  2016-11-11  6:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-05  4:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26c4b26f0cc51f04cdaba3c9e6ff09032bd10d8b ***

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

Fix a few typos

gdb/ChangeLog:

	* maint.c (scoped_command_stats::scoped_command_stats): Fix typo.
	* ppcnbsd-tdep.c (_initialize_ppcnbsd_tdep): Likewise.
	* ppcobsd-tdep.c (_initialize_ppcobsd_tdep): Likewise.
	* ui-out.c (ui_out_new): Likewise.
	* utils.c (init_page_info): Likewise.
	(reset_prompt_for_continue_wait_time): Likewise.
	* windows-nat.c (windows_init_thread_list): Likewise.
	* xtensa-tdep.c (call0_analyze_prologue): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] i386-tdep.c (i386_gdbarch_init): Add comments.
@ 2016-11-08  0:39 sergiodj+buildbot
  2016-11-12  0:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-08  0:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad9eb1fdda263cd91ee8fb36292fb29d546b0076 ***

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

i386-tdep.c (i386_gdbarch_init): Add comments.

gdb/ChangeLog:

	* i386-tdep.c (i386_gdbarch_init): Add comments.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] X86: Properly handle bad FPU opcode
@ 2016-11-08  2:27 sergiodj+buildbot
  2016-11-12 10:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-08  2:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 48c97fa1ba7d6628352fc2433abd91a41f6c8171 ***

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

X86: Properly handle bad FPU opcode

Since Bad_Opcode and FGRPd9_2 were the same in i386-dis.c, all
Bad_Opcode entries in float_reg were displaced as FGRPd9_2.  This
patch adds an entry for Bad_Opcode in fgrps to avoid treating it
as FGRPd9_2.

gas/

	PR binutils/20775
	* testsuite/gas/i386/i386.exp: Run fpu-bad.
	* testsuite/gas/i386/fpu-bad.d: New file.
	* testsuite/gas/i386/fpu-bad.s: Likewise.

opcodes/

	PR binutils/20775
	* i386-dis.c (FGRPd9_2): Replace 0 with 1.
	(FGRPd9_4): Replace 1 with 2.
	(FGRPd9_5): Replace 2 with 3.
	(FGRPd9_6): Replace 3 with 4.
	(FGRPd9_7): Replace 4 with 5.
	(FGRPda_5): Replace 5 with 6.
	(FGRPdb_4): Replace 6 with 7.
	(FGRPde_3): Replace 7 with 8.
	(FGRPdf_4): Replace 8 with 9.
	(fgrps): Add an entry for Bad_Opcode.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove arm_insert_single_step_breakpoint
@ 2016-11-08 14:37 sergiodj+buildbot
  2016-11-13  7:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-08 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 771da62d67a9f27c1e706610efe51b13c3f9fd60 ***

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

Remove arm_insert_single_step_breakpoint

This patch is to remove arm_insert_single_step_breakpoint.

gdb:

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

	* arm-linux-tdep.c (arm_linux_software_single_step): Don't
	call arm_insert_single_step_breakpoint, call
	insert_single_step_breakpoint instead.
	* arm-tdep.c (arm_insert_single_step_breakpoint): Remove.
	(arm_software_single_step): Don't call
	arm_insert_single_step_breakpoint, call
	insert_single_step_breakpoint instead.
	* arm-tdep.h (arm_insert_single_step_breakpoint): Remove
	declaration.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step returns VEC (CORE_ADDR) *
@ 2016-11-08 17:10 sergiodj+buildbot
  2016-11-13 16:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-08 17:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93f9a11fbdb8f09428b17180d51a09a1bda39a52 ***

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

gdbarch software_single_step returns VEC (CORE_ADDR) *

This patch changes gdbarch method software_single_step to return a
vector of addresses on which GDB should insert breakpoints, and don't
insert breakpoints.  Instead, the caller of
gdbarch_software_single_step inserts breakpoints if the returned
vector is not NULL.

gdb:

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

	* aarch64-tdep.c (aarch64_software_single_step): Return
	VEC (CORE_ADDR) *.  Return NULL instead of 0.  Don't call
	insert_single_step_breakpoint.
	* alpha-tdep.c (alpha_deal_with_atomic_sequence): Likewise.
	(alpha_software_single_step): Likewise.
	* alpha-tdep.h (alpha_software_single_step): Update declaration.
	* arm-linux-tdep.c (arm_linux_software_single_step): Return
	VEC (CORE_ADDR) *.  Return NULL instead of 0.
	* arm-tdep.c (arm_software_single_step): Return NULL instead of	0.
	* arm-tdep.h (arm_software_single_step): Update declaration.
	* breakpoint.c (insert_single_step_breakpoints): New function.
	* breakpoint.h (insert_single_step_breakpoints): Declare.
	* cris-tdep.c (cris_software_single_step): Return
	VEC (CORE_ADDR) *.  Don't call insert_single_step_breakpoint.
	* gdbarch.sh (software_single_step): Change it to return
	VEC (CORE_ADDR) *.
	* gdbarch.c, gdbarch.h: Regenerated.
	* infrun.c (maybe_software_singlestep): Adjust.
	* mips-tdep.c (mips_deal_with_atomic_sequence): Return
	VEC (CORE_ADDR) *.  Don't call insert_single_step_breakpoint.
	(micromips_deal_with_atomic_sequence): Likewise.
	(deal_with_atomic_sequence): Likewise.
	(mips_software_single_step): Likewise.
	* mips-tdep.h (mips_software_single_step): Update declaration.
	* moxie-tdep.c (moxie_software_single_step): Likewise.
	* nios2-tdep.c (nios2_software_single_step): Likewise.
	* ppc-tdep.h (ppc_deal_with_atomic_sequence): Update
	declaration.
	* record-full.c (record_full_resume): Adjust.
	(record_full_wait_1): Likewise.
	* rs6000-aix-tdep.c (rs6000_software_single_step): Return
	VEC (CORE_ADDR) *.  Don't call insert_single_step_breakpoint.
	* rs6000-tdep.c	(ppc_deal_with_atomic_sequence): Return
	VEC (CORE_ADDR) *.  Don't call insert_single_step_breakpoint.
	* s390-linux-tdep.c (s390_software_single_step): Likewise.
	* sparc-tdep.c (sparc_software_single_step): Likewise.
	* spu-tdep.c (spu_software_single_step): Likewise.
	* tic6x-tdep.c (tic6x_software_single_step): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] breakpoint.c:commands_command_1 constification and cleanup
@ 2016-11-08 18:27 sergiodj+buildbot
  2016-11-14  6:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-08 18:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 896b6bda6904765f36692d76a37b99c0412ca9ae ***

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

breakpoint.c:commands_command_1 constification and cleanup

This is constification needed for next patch.  Adjust
commands_command_1 to use std::string too because the "arg" parameter
is currently overwritten and then passed to make_cleanup.  The
constification alone would trigger a compile error in the make_cleanup
call otherwise (passing const char * to void * parameter).  Using
std::string gets rid of the cleanup in the first place, resulting in
simpler code.

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

	* breakpoint.c (struct commands_info) <arg>: Constify.
	(commands_command_1): Constify 'arg' parameter.  Use std::string
	and string_printf.
	(commands_from_control_command): Constify 'arg' parameter.
	(map_breakpoint_numbers): Constify 'args' parameter.
	* breakpoint.h (commands_from_control_command): Constify 'arg'
	parameter.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] cli/cli-script.c: Remove some dead NULL checks
@ 2016-11-08 19:48 sergiodj+buildbot
  2016-11-14  2:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-08 19:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f8ad951f662864884d4b11315c940c5239a4a89 ***

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

cli/cli-script.c: Remove some dead NULL checks

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

	* cli/cli-script.c (execute_control_command): Assume insert_args
	never returns NULL.
	(insert_args): Assume xmalloc never returns NULL.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/xtensa-tdep.c
@ 2016-11-08 23:42 sergiodj+buildbot
  2016-11-15  6:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-08 23:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0f86e735886f3d373507fa9cfc0cf2a2f32eabc ***

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

Use ui_file_as_string in gdb/xtensa-tdep.c

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

	* xtensa-tdep.c (xtensa_verify_config): Use ui_file_as_string and
	std::string.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/arm-tdep.c
@ 2016-11-09  3:33 sergiodj+buildbot
  2016-11-15 22:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-09  3:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09b0e4b047b44063cf4c8c00527886743619c24e ***

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

Use ui_file_as_string in gdb/arm-tdep.c

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

	* arm-tdep.c (_initialize_arm_tdep): Use ui_file_as_string and
	std::string.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/cli/cli-setshow.c
@ 2016-11-09  9:53 sergiodj+buildbot
  2016-11-17  8:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-09  9:53 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdbarch.sh/gdbarch.c
@ 2016-11-09 12:46 sergiodj+buildbot
  2016-11-17 20:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 12:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f0302493af0ace93943041c3374069c15c363f7 ***

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

Use ui_file_as_string in gdbarch.sh/gdbarch.c

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

	* gdbarch.sh (verify_gdbarch): Use ui_file_as_string and
	std::string.
	* gdbarch.c: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Eliminate agent_expr_p; VEC -> std::vector in struct bp_target_info
@ 2016-11-09 18:42 sergiodj+buildbot
  2016-11-19  2:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 18:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3cde5c42d1c1ddcf8bbde5c47233c644370c959c ***

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

Eliminate agent_expr_p; VEC -> std::vector in struct bp_target_info

After the previous patch, we end up with these two types with quite
similar, and potentially confusing names:

  typedef gdb::unique_ptr<agent_expr> agent_expr_up;

  /* Pointer to an agent_expr structure.  */
  typedef struct agent_expr *agent_expr_p;

The latter is only necessary to put agent_expr pointers in VECs.  So
just eliminate it and use std::vector instead.

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

	* ax.h (agent_expr_p): Delete.
	(DEF_VEC_P (agent_expr_p)): Delete.
	* breakpoint.c (build_target_condition_list)
	(build_target_command_list): Adjust to use of std::vector.
	(bp_location_dtor): Remove now unnecessary VEC_free calls.
	* breakpoint.h: Include <vector>.
	(struct bp_target_info) <conditions, tcommands>: Now
	std::vector's.
	* remote.c (remote_add_target_side_condition): bp_tgt->conditions
	is now a std::vector; adjust.
	(remote_add_target_side_commands, remote_insert_breakpoint):
	bp_tgt->tcommands is now a std::vector; adjust.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] X86: Remove the THREE_BYTE_0F7A entry
@ 2016-11-09 23:16 sergiodj+buildbot
  2016-11-20  2:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 23:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f334aeb2268db153f01143e9b0ac01448ecaa56 ***

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

X86: Remove the THREE_BYTE_0F7A entry

Remove the THREE_BYTE_0F7A entry which is leftover from SSE5.

	PR binutils/20701
	* i386-dis.c (THREE_BYTE_0F7A): Removed.
	(dis386_twobyte): Don't use THREE_BYTE_0F7A.
	(three_byte_table): Remove THREE_BYTE_0F7A.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] tui-winsource: Allocate for actual lines only
@ 2016-11-10  3:59 sergiodj+buildbot
  2016-11-20 18:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  3:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7bc2c8b83ea82b4315c67e7658af815aed062e73 ***

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

tui-winsource: Allocate for actual lines only

The logic for allocating a TUI source window's content buffer allocates
two more lines than needed, because it does not reduce the window height
by the highlight box's overhead.  However, it does reduce the line width
accordingly.  This patch makes the height and width calculation
consistent and improves the comment.

gdb/ChangeLog:

	* tui/tui-winsource.c (tui_alloc_source_buffer): Subtract
	highlight box's overhead when calculating the content height.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] agent_expr_up: gdb::unique_ptr -> std::unique_ptr
@ 2016-11-10  7:45 sergiodj+buildbot
  2016-11-21  8:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c73cd95f96d37dbf6092a87c8ba0f35277223a5 ***

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

agent_expr_up: gdb::unique_ptr -> std::unique_ptr

Now that we require C++11, use std::unique_ptr directly.  This allows
simplifying collection_list a bit by placing unique pointers in the
vector directly, making the vector own its elements.

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

	* ax-gdb.c (agent_eval_command_one): Use std::move instead of
	gdb::move.
	* ax.h (agent_expr_up): Use std::unique_ptr instead of
	gdb::unique_ptr.
	* breakpoint.c (parse_cond_to_aexpr): Use std::move instead of
	gdb::move.
	* tracepoint.c (collection_list::collect_symbol): Likewise.
	(collection_list::~collection_list): Delete.
	(encode_actions_1): Use std::move instead of gdb::move.
	(collection_list::add_aexpr): Use std::move instead of
	unique_ptr::release.
	* tracepoint.h (collection_list) <~collection_list>: Delete
	declaration.
	<m_aexprs>: Now a vector of agent_ptr_up.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix
@ 2016-11-10  7:46 sergiodj+buildbot
  2016-11-21 16:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8354c62cd144964fce17e11ce035c0c2c0635cbf ***

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

Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix

Pedro's patch provides a cleaner way to prefix tests with the proc name,
so let's use that.

gdb/testsuite/ChangeLog:

	* gdb.mi/user-selected-context-sync.exp (with_test_prefix_procname):
	Remove.
	(test_setup): Define with proc_with_prefix.
	(test_cli_inferior): Likewise.
	(test_cli_thread): Likewise.
	(test_cli_frame): Likewise.
	(test_cli_select_frame): Likewise.
	(test_cli_up_down): Likewise.
	(test_mi_thread_select): Likewise.
	(test_mi_stack_select_frame): Likewise.
	(test_cli_in_mi_inferior): Likewise.
	(test_cli_in_mi_thread): Likewise.
	(test_cli_in_mi_frame): Likewise.
	(top level): Do not use with_test_prefix_procname.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Bind defined symbol locally in PIE
@ 2016-11-10  9:30 sergiodj+buildbot
  2016-11-22 14:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  9:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac33b731d214d79738ca04d27f7464d4482f6a01 ***

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

[AArch64] Bind defined symbol locally in PIE

bfd/
	PR target/20737
	* elfnn-aarch64.c (elfNN_aarch64_final_link_relocate): Bind defined
	symbol locally in PIE.

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: mips: fix builds for r3900 cpus due to missing check_u64
@ 2016-11-11  9:01 sergiodj+buildbot
  2016-11-23  7:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e04659e8607bfed6995fd2ced9aaab55e2143302 ***

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

sim: mips: fix builds for r3900 cpus due to missing check_u64


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] sim: mips: fix dv-tx3904cpu build error
@ 2016-11-11 10:09 sergiodj+buildbot
  2016-11-23 11:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 10:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91588b3af8e026ba11c7368476cc1f3fa8c2e2b1 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 91588b3af8e026ba11c7368476cc1f3fa8c2e2b1

sim: mips: fix dv-tx3904cpu build error

When building for mipstx39-rtems4.12 targets, some funcs use SD and CPU
implicitly.  Restore the defines for these to the local sd and cpu vars.

This was broken by the clean up in commit d47f5b30d8481272e9480118bdcb.

Reported-by: Joel Sherrill <joel.sherrill@oarcorp.com>


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove parameter valaddr from c print functions
@ 2016-11-11 10:40 sergiodj+buildbot
  2016-11-23 15:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 10:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 65408fa680538f997cdd4b6fb9d74f043a060801 ***

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

Remove parameter valaddr from c print functions

This patch removes parameter valaddr from some c print functions.

gdb:

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

	* c-lang.h (cp_print_value_fields): Update declaration.
	* cp-valprint.c (cp_print_value): Update declaration.
	(cp_print_value_fields): Remove parameter valaddr.  Callers
	updated.
	(cp_print_value): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove apply_val_pretty_printer parameter valaddr
@ 2016-11-11 12:02 sergiodj+buildbot
  2016-11-23 17:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 668e167446b2777869f413841ec05aed59473d9f ***

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

Remove apply_val_pretty_printer parameter valaddr

This patch removes the parameter valaddr of
extension_language_ops::apply_val_pretty_printer and remove const from
"struct value *val".  valaddr can be got in each extension language's
implementation of apply_val_pretty_printer.

gdb:

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

	* cp-valprint.c (cp_print_value): Remove local base_valaddr.
	* extension-priv.h (struct extension_language_ops)
	<apply_val_pretty_printer>: Remove the second parameter.
	Remove const from "struct value *".  Callers updated.
	* extension.c (apply_ext_lang_val_pretty_printer): Update
	comments.  Remove parameter valaddr.  Remove const from
	"struct value *".
	* extension.h (apply_ext_lang_val_pretty_printer): Update
	declaration.
	* guile/guile-internal.h (gdbscm_apply_val_pretty_printer):
	Update declaration.
	* guile/scm-pretty-print.c (gdbscm_apply_val_pretty_printer):
	Remove parameter valaddr.  Remove const from "struct value *".
	* python/py-prettyprint.c (gdbpy_apply_val_pretty_printer):
	Likewise.
	* python/python-internal.h (gdbpy_apply_val_pretty_printer):
	Update declaration.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Accept hidden COFF symbols, but treat them as if they were debugging symbols.
@ 2016-11-11 12:40 sergiodj+buildbot
  2016-11-23 21:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 12:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7103ad7639b7ed80bec170404185a8e39079446b ***

Author: Luke Allardyce <lukeallardyce@gmail.com>
Branch: master
Commit: 7103ad7639b7ed80bec170404185a8e39079446b

Accept hidden COFF symbols, but treat them as if they were debugging symbols.

	PR ld/20722
	* coffcode.h (coff_slurp_symbol_table): Accept C_HIDDEN symbols,
	but treat them as debugging symbols.


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

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

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

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

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

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

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

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Increase max_num_aliases in aarch64-gen
@ 2016-11-11 14:42 sergiodj+buildbot
  2016-11-24  3:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 14:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d731f6949e2b0099cfbe0cf608d60a52a66d354 ***

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

[AArch64] Increase max_num_aliases in aarch64-gen

Some ARMv8.3 pointer authentication instructions are encoded as HINT aliases,
so to allow more instruction aliases in the generator, max_num_aliases is
increased from 16 to 32.

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

	* aarch64-gen.c (find_alias_opcode): Increase max_num_aliases to 32.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 instructions which are in the NOP space
@ 2016-11-11 15:42 sergiodj+buildbot
  2016-11-24  8:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 15:42 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

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

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

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

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

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 pointer authentication key registers
@ 2016-11-11 16:38 sergiodj+buildbot
  2016-11-24 11:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 16:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b0bfa7b5b884f78b798ab8d34d2a50bc63f558df ***

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

[AArch64] Add ARMv8.3 pointer authentication key registers

Add support for system registers introduced in ARMv8.3
for pointer authentication.

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

	* aarch64-opc.c (aarch64_sys_regs): Add apiakeylo_el1, apiakeyhi_el1,
	apibkeylo_el1, apibkeyhi_el1, apdakeylo_el1, apdakeyhi_el1,
	apdbkeylo_el1, apdbkeyhi_el1, apgakeylo_el1 and apgakeyhi_el1.
	(aarch64_sys_reg_supported_p): Add feature test for new registers.

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

	* testsuite/gas/aarch64/sysreg-3.s: New.
	* testsuite/gas/aarch64/sysreg-3.d: New.
	* testsuite/gas/aarch64/illegal-sysreg-3.l: New.
	* testsuite/gas/aarch64/illegal-sysreg-3.d: New.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 single source PAC instructions
@ 2016-11-11 17:32 sergiodj+buildbot
  2016-11-24 14:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 17:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2cfc830e715142a0dd28496feaedf569b116b0e ***

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

[AArch64] Add ARMv8.3 single source PAC instructions

Add support for ARMv8.3 pointer authentication instructions
that are encoded as single source data processing instructions.

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

	* aarch64-tbl.h (arch64_opcode_table): Add pacia, pacib, pacda, pacdb, autia,
	autib, autda, autdb, paciza, pacizb, pacdza, pacdzb, autiza, autizb, autdza,
	autdzb, xpaci, xpacd.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.

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

	* testsuite/gas/aarch64/pac.s: New.
	* testsuite/gas/aarch64/pac.d: New.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 PACGA instruction
@ 2016-11-11 18:47 sergiodj+buildbot
  2016-11-24 17:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c84364ece4faa7b3eb0f60f4dc301282e9693e1e ***

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

[AArch64] Add ARMv8.3 PACGA instruction

Add support for the ARMv8.3 PACGA instruction.

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

	* opcode/aarch64.h (enum aarch64_opnd): Add AARCH64_OPND_Rm_SP.

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

	* aarch64-tbl.h (arch64_opcode_table): Add pacga.
	(AARCH64_OPERANDS): Add Rm_SP.
	* aarch64-opc.c (aarch64_print_operand): Handle AARCH64_OPND_Rm_SP.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.

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

	* config/tc-aarch64.c (process_omitted_operand): Handle AARCH64_OPND_Rm_SP.
	(parse_operands): Likewise.
	* testsuite/gas/aarch64/pac.s: Add pacga.
	* testsuite/gas/aarch64/pac.d: Add pacga.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 combined pointer authentication branch instructions
@ 2016-11-11 19:33 sergiodj+buildbot
  2016-11-24 20:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 19:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74f5402d08b857d60499b27851c204954ce6c42c ***

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

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

Add support for ARMv8.3 pointer authentication instructions
that are encoded as unconditional branch instructions.

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

	* aarch64-tbl.h (arch64_opcode_table): Add braa, brab, blraa, blrab, braaz,
	brabz, blraaz, blrabz, retaa, retab, eretaa, eretab.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.

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

	* testsuite/gas/aarch64/pac.s: Add ARMv8.3 branch instruction tests.
	* testsuite/gas/aarch64/pac.d: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Identify verilog dump tests as such.
@ 2016-11-11 20:35 sergiodj+buildbot
  2016-11-25  0:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 20:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f8db343049c3e06483a278e14b7e140ec55c8b3 ***

Author: Catherine Moore <clm@codesourcery.com>
Branch: master
Commit: 1f8db343049c3e06483a278e14b7e140ec55c8b3

Identify verilog dump tests as such.

	A couple of the verilog dump tests were marked as ihex tests.  This
	patch identifies the tests as verilog format dump tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't handle unavailable/optimized-out in spu_software_single_step
@ 2016-11-11 21:18 sergiodj+buildbot
  2016-11-25  4:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 21:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d15592e06e4abccc97cb8c5670f564327f747e9 ***

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

Don't handle unavailable/optimized-out in spu_software_single_step

When we do software single step, frame is always the innermost one,
so it is impossible to get unavailable/optimized-out errors.

gdb:

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

	* spu-tdep.c (spu_software_single_step): Don't call
	get_frame_register_bytes, call get_frame_register_unsigned
	instead.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use std::string in rust_get_disr_info
@ 2016-11-12 19:05 sergiodj+buildbot
  2016-11-25  7:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-12 19:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d93f4d96bb0fb307db9e2dade38ddb3c6bc469ca ***

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

Use std::string in rust_get_disr_info

This changes rust_get_disr_info to use std::string in one more spot,
avoiding a memory leak.

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

	* rust-lang.c (rust_get_disr_info): Use std::string in one more
	spot.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove some cleanups from the rust code
@ 2016-11-12 20:45 sergiodj+buildbot
  2016-11-25 10:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-12 20:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8001f1183f32d674fa3e9af1cca16856afdffc3e ***

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

Remove some cleanups from the rust code

This removes some cleanups from the rust code, in favor of C++ objects
with destructors.

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

	* rust-exp.y (super_name): Use std::vector.
	(lex_number): Use std::string.
	(convert_params_to_types): Return std::vector.
	(convert_ast_to_type, convert_name): Update.
	* rust-lang.c (rust_get_disr_info): Use unique_xmalloc_ptr.


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

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

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] btrace: read entire aux buffer
@ 2016-11-14 10:28 sergiodj+buildbot
  2016-11-26  5:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-14 10:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db58b3735f45345c06cb9a14d0f83f5b26c1ebf3 ***

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

btrace: read entire aux buffer

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

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

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

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

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

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

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

Change-Id: If4f8049a2080a5f16f336309450b32a3eb1e3ec9


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Also check GOT PLT for R_X86_64_PLTOFF64
@ 2016-11-14 19:27 sergiodj+buildbot
  2016-11-26 10:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-14 19:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d734efa1034d266249751978f95a686ec9d19c6 ***

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

Also check GOT PLT for R_X86_64_PLTOFF64

Since "-z now" replaces PLT with GOT PLT, we should also check GOT PLT
for R_X86_64_PLTOFF64 relocation.

bfd/

	PR ld/20800
	* elf64-x86-64.c (elf_x86_64_relocate_section): Also check
	plt_got.offset for R_X86_64_PLTOFF64.

ld/

	PR ld/20800
	* testsuite/ld-x86-64/pr20800a.S: New file.
	* testsuite/ld-x86-64/pr20800b.S: Likewise.
	* testsuite/ld-x86-64/x86-64.exp: Run PR ld/20800 test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] bitfield-parent-optimized-out: Fix struct definition
@ 2016-11-15 20:24 sergiodj+buildbot
  2016-11-26 15:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-15 20:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7f38fdae7c75e1d13abd455b3931950db28d22b ***

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

bitfield-parent-optimized-out: Fix struct definition

The "struct S" type in bitfield-parent-optimized-out.exp is declared to
have a size of 4 bytes but to hold two 4-byte members: an int-based
bitfield and a 4-byte int.  Also, both members have the same
data_member_location 2, causing them to overlap and to reach 2 bytes
beyond the structure's boundary.

This is fixed by increasing the structure size to 8 and setting the
first and second member's data_member_location to 0 and 4, respectively.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/bitfield-parent-optimized-out.exp: Fix DWARF code for
	the definition of struct S.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb::{unique_ptr,move} -> std::{unique_ptr,move}
@ 2016-11-15 20:54 sergiodj+buildbot
  2016-11-26 15:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-15 20:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b22e99fdaf2efe58161c382bbd55f4572ba49eef ***

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

gdb::{unique_ptr,move} -> std::{unique_ptr,move}

Now that we require C++11, use std::unique_ptr and std::move directly.

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

	* ada-lang.c (create_excep_cond_exprs): Use std::move instead of
	gdb::move.
	* break-catch-throw.c (handle_gnu_v3_exceptions): Use
	std::unique_ptr instead of gdb::unique_ptr.
	* breakpoint.c (watch_command_1): Use std::move instead of
	gdb::move.
	* cli/cli-dump.c (dump_memory_to_file, restore_binary_file): Use
	std::unique_ptr instead of gdb::unique_ptr.
	* dtrace-probe.c (dtrace_process_dof_probe): Use std::move instead
	of gdb::move.
	* elfread.c (elf_read_minimal_symbols): Use std::unique_ptr
	instead of gdb::unique_ptr.
	* mi/mi-main.c (mi_cmd_data_read_memory): Use std::unique_ptr
	instead of gdb::unique_ptr.
	* parse.c (parse_expression_for_completion): Use std::move instead
	of gdb::move.
	* printcmd.c (display_command): std::move instead of gdb::move.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Delete gdb::unique_ptr/gdb::move
@ 2016-11-15 22:01 sergiodj+buildbot
  2016-11-26 19:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-15 22:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5cc8c7310338224d65aa14c4256d4d7539e0dd45 ***

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

Delete gdb::unique_ptr/gdb::move

Now that we require C++11 and all uses of gdb::unique_ptr and
gdb::move are gone, let's remove their definitions...

With my lazy hat on, I repurposed the header for "generally useful
unique_ptr specializations", and left gdb::unique_xmalloc_ptr in
there.  Not sure whether we it'd be better move it out of the gdb
namespace or leave it be.  I left it because it's less work and avoids
disrupting yet-unmerged patches that use it.

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

	* common/common-defs.h: Update comment.
	* common/gdb_unique_ptr.h: Update header comment and copyright
	year.
	(gdb::unique_ptr, gdb::move): Delete.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: update gnulib to pull in C++ namespace support fixes
@ 2016-11-16  0:24 sergiodj+buildbot
  2016-11-26 22:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-16  0:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c62b19fd2e6b81ce7cbb7d01e84c09352ccf224 ***

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

gdb: update gnulib to pull in C++ namespace support fixes

I've been experimenting with making use of gnulib's C++ namespace support:

 https://www.gnu.org/software/gnulib/manual/html_node/A-C_002b_002b-namespace-for-gnulib.html

That stumbled on a few gnulib issues, which I've fixed upstream:

 [PATCH] Fix gnulib C++ namespace support and std::frexp
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00039.html

 [PATCH] Fix real-floating argument functions in C++ mode
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00049.html

 [PATCH] Avoid having GNULIB_NAMESPACE::func always inject references to rpl_func
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00040.html

 [PATCH] C++: "#define timeval rpl_timeval" -> typedef in GNULIB_NAMESPACE
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00058.html

This merge pulls those in.

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

	* gnulib/update-gnulib.sh (GNULIB_COMMIT_SHA1): Set to
	38237baf99386101934cd93278023aa4ae523ec0.
	* gnulib/configure, gnulib/config.in: Regenerate.
	* gnulib/import/Makefile.am: Regenerate.
	* gnulib/import/Makefile.in: Regenerate.
	* gnulib/import/canonicalize-lgpl.c: Update.
	* gnulib/import/extra/snippet/c++defs.h: Update.
	* gnulib/import/m4/stdint.m4: Update.
	* gnulib/import/m4/stdlib_h.m4: Update.
	* gnulib/import/math.in.h: Update.
	* gnulib/import/stdlib.in.h: Update.
	* gnulib/import/sys_time.in.h: Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR20789 - relaxation with negative valued diff relocs
@ 2016-11-16 20:01 sergiodj+buildbot
  2016-11-27  2:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4cb771f214ed6a2102e37bce255c6be5d0642f3a ***

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

Fix PR20789 - relaxation with negative valued diff relocs

Fix issues with diff relocs that have a negative value
i.e. sym2 - sym1 where sym2 is lesser than sym1.

The assembler generates a diff reloc with symbol as start of section
and addend as sym2 offset, and encodes assembly time difference at
the reloc offset.

The existing relaxation logic adjusts addends if the relaxed insn lies
between symbol and addend. That doesn't work for diff relocs where
sym2 is less than sym1 *and* the relaxed insn happens to be between
sym2 and sym1.

Fix the problems by

1. Using signed handling of the difference value (bfd_signed_vma instead
of bfd_vma, bfd_{get,set}_signed_xxx instead of bfd_{get,set}_xxx).

2. Not assuming sym2 is bigger than sym1. It instead computes the actual
addresses and sets the lower and higher addresses as start and end
addresses respectively and then sees if insn is between start and end.

3. Creating a new function elf32_avr_adjust_reloc_if_spans_insn to
centralize reloc adjustment, and ensuring diff relocs get adjusted
correctly even if their sym + addend doesn't overlap a relaxed insn.

It also removes a redundant variable did_pad. It is never set if
did_shrink is TRUE, and the code does a early return if did_shrink is
FALSE.

bfd/ChangeLog

2016-11-15  Senthil Kumar Selvaraj  <senthil_kumar.selvaraj@atmel.com>

       PR ld/20789
       * bfd/elf32-avr.c (elf32_avr_adjust_diff_reloc_value): Do signed
       manipulation of diff value, and don't assume sym2 is less than sym1.
       (elf32_avr_adjust_reloc_if_spans_insn): New function.
       (elf32_avr_relax_delete_bytes): Use elf32_avr_adjust_diff_reloc_value,
       and remove redundant did_pad.

ld/ChangeLog

2016-11-15  Senthil Kumar Selvaraj  <senthil_kumar.selvaraj@atmel.com>

       PR ld/20789
       * ld/testsuite/ld-avr/pr20789.d: New test.
       * ld/testsuite/ld-avr/pr20789.s: New test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Extend test gdb.python/py-recurse-unwind.exp
@ 2016-11-16 20:03 sergiodj+buildbot
  2016-11-28 16:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 20:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a2f3d7ff1d79b1290704e48c71e905b987393a6 ***

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

Extend test gdb.python/py-recurse-unwind.exp

This patch modifies the unwinder (sniffer) defined in
py-recurse-unwind.py so that, depending upon the value of one of its
class variables, it will take different paths through the code,
testing different functionality.

The original test attempted to obtain the value of an undefined
symbol.

This somewhat expanded test checks to see if 'pc' can be read via
gdb.PendingFrame.read_register() and also via gdb.parse_and_eval().

gdb/testsuite/ChangeLog:

	* gdb.python/py-recurse-unwind.c (main): Add loop.
	* gdb.python/py-recurse-unwind.py (TestUnwinder): Add calls
	to read_register() and gdb.parse_and_eval().  Make each code
	call a separate case that can be individually tested.
	* gdb.python/py-recurse-unwind.exp (cont_and_backtrace): New
	proc. Call cont_and_backtrace for each of the code paths that
	we want to test in the unwinder.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Distinguish sentinel frame from null frame.
@ 2016-11-16 21:50 sergiodj+buildbot
  2016-11-28 19:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df433d316277ff5293832d3cd6cbc30b5c38dec0 ***

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

Distinguish sentinel frame from null frame.

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

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

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

Thanks to Pedro Alves for this suggestion.

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Change meaning of VALUE_FRAME_ID; rename to VALUE_NEXT_FRAME_ID
@ 2016-11-16 22:04 sergiodj+buildbot
  2016-11-28 23:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 22:04 UTC (permalink / raw)
  To: gdb-testers

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

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

Change meaning of VALUE_FRAME_ID; rename to VALUE_NEXT_FRAME_ID

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

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

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

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

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

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

This patch implements this idea.

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

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

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

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

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Make gdb.PendingFrame.read_register handle "user" registers.
@ 2016-11-16 22:59 sergiodj+buildbot
  2016-11-29  3:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 22:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33cc7d368f420326606695daafd6292e2779c6af ***

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

Make gdb.PendingFrame.read_register handle "user" registers.

The C function, pending_framepy_read_register(), which implements
the python interface gdb.PendingFrame.read_register does not handle
the so called "user" registers like "pc".  An assertion error is
triggered due to the user registers having numbers larger than or
equal to gdbarch_num_regs(gdbarch).

With the VALUE_FRAME_ID tweak in place, the call to
get_frame_register_value() can simply be replaced by a call to
value_of_register(), which handles both real registers as well as the
user registers.

gdb/ChangeLog:

	* python/py-unwind.c (pending_framepy_read_register): Use
	value_of_register() instead of get_frame_register_value().


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Stash frame id of current frame before stashing frame id for previous frame
@ 2016-11-17  0:20 sergiodj+buildbot
  2016-11-29  6:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-17  0:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 256ae5dbc73d1348850f86ee77a0dc3b04bc7cc0 ***

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

Stash frame id of current frame before stashing frame id for previous frame

This patch ensures that the frame id for the current frame is stashed
before that of the previous frame (to the current frame).

First, it should be noted that the frame id for the current frame is
not stashed by get_current_frame().  The current frame's frame id is
lazily computed and stashed via calls to get_frame_id().  However,
it's possible for get_prev_frame() to be called without first stashing
the current frame.

The frame stash is used not only to speed up frame lookups, but
also to detect cycles.  When attempting to compute the frame id
for a "previous" frame (in get_prev_frame_if_no_cycle), a cycle
is detected if the computed frame id is already in the stash.

If it should happen that a previous frame id is stashed which should
represent a cycle for the current frame, then an assertion failure
will trigger should get_frame_id() be later called to determine
the frame id for the current frame.

As of late 2016, with the "Tweak meaning of VALUE_FRAME_ID" patch in
place, this actually occurs when running the
gdb.dwarf2/dw2-dup-frame.exp test.  While attempting to generate a
backtrace, the python frame filter code is invoked, leading to
frame_info_to_frame_object() (in python/py-frame.c) being called.
That function will potentially call get_prev_frame() before
get_frame_id() is called.  The call to get_prev_frame() can eventually
end up in get_prev_frame_if_no_cycle() which, in turn, calls
compute_frame_id(), after which the frame id is stashed for the
previous frame.

If the frame id for the current frame is stashed, the cycle detection
code (which relies on the frame stash) in get_prev_frame_if_no_cycle()
will be triggered for a cycle starting with the current frame.  If the
current frame's id is not stashed, the cycle detecting code can't
operate as designed.  Instead, when get_frame_id() is called on the
current frame at some later point, the current frame's id will found
to be already in the stash, triggering an assertion failure.

Below is an in depth examination of the failure which lead to this change.
I've shortened pathnames for brevity and readability.

Here's the portion of the log file showing the failure/internal error:

(gdb) break stop_frame
Breakpoint 1 at 0x40059a: file dw2-dup-frame.c, line 22.
(gdb) run
Starting program: testsuite/outputs/gdb.dwarf2/dw2-dup-frame/dw2-dup-frame

Breakpoint 1, stop_frame () at dw2-dup-frame.c:22
22	}
(gdb) bt
gdb/frame.c:544: internal-error: frame_id get_frame_id(frame_info*): Assertion `stashed' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
FAIL: gdb.dwarf2/dw2-dup-frame.exp: backtrace from stop_frame (GDB internal error)

Here's a partial backtrace from the internal error, showing the frames
which I think are relevant, plus several extra to provide context:

    #0  internal_error (
	file=0x932b98 "gdb/frame.c", line=544,
	fmt=0x932b20 "%s: Assertion `%s' failed.")
	at gdb/common/errors.c:54
    #1  0x000000000072207e in get_frame_id (fi=0xe5a760)
	at gdb/frame.c:544
    #2  0x00000000004eb50d in frame_info_to_frame_object (frame=0xe5a760)
	at gdb/python/py-frame.c:390
    #3  0x00000000004ef5be in bootstrap_python_frame_filters (frame=0xe5a760,
	frame_low=0, frame_high=-1)
	at gdb/python/py-framefilter.c:1453
    #4  0x00000000004ef7a9 in gdbpy_apply_frame_filter (
	extlang=0x8857e0 <extension_language_python>, frame=0xe5a760, flags=7,
	args_type=CLI_SCALAR_VALUES, out=0xf6def0, frame_low=0, frame_high=-1)
	at gdb/python/py-framefilter.c:1548
    #5  0x00000000005f2c5a in apply_ext_lang_frame_filter (frame=0xe5a760,
	flags=7, args_type=CLI_SCALAR_VALUES, out=0xf6def0, frame_low=0,
	frame_high=-1)
	at gdb/extension.c:572
    #6  0x00000000005ea896 in backtrace_command_1 (count_exp=0x0, show_locals=0,
	no_filters=0, from_tty=1)
	at gdb/stack.c:1834

Examination of the code in frame_info_to_frame_object(), which is in
python/py-frame.c, is key to understanding this problem:

      if (get_prev_frame (frame) == NULL
	  && get_frame_unwind_stop_reason (frame) != UNWIND_NO_REASON
	  && get_next_frame (frame) != NULL)
	{
	  frame_obj->frame_id = get_frame_id (get_next_frame (frame));
	  frame_obj->frame_id_is_next = 1;
	}
      else
	{
	  frame_obj->frame_id = get_frame_id (frame);
	  frame_obj->frame_id_is_next = 0;
	}

I will first note that the frame id for frame has not been computed yet.  (This
was verified by placing a breakpoint on compute_frame_id().)

The call to get_prev_frame() causes the the frame id to (eventually) be
computed for the previous frame.  Here's a backtrace showing how we
get there:

    #0  compute_frame_id (fi=0x10e2810)
	at gdb/frame.c:496
    #1  0x0000000000724a67 in get_prev_frame_if_no_cycle (this_frame=0xe5a760)
	at gdb/frame.c:1871
    #2  0x0000000000725136 in get_prev_frame_always_1 (this_frame=0xe5a760)
	at gdb/frame.c:2045
    #3  0x000000000072516b in get_prev_frame_always (this_frame=0xe5a760)
	at gdb/frame.c:2061
    #4  0x000000000072570f in get_prev_frame (this_frame=0xe5a760)
	at gdb/frame.c:2303
    #5  0x00000000004eb471 in frame_info_to_frame_object (frame=0xe5a760)
	at gdb/python/py-frame.c:381

For this particular case, we end up in the else clause of the code above
which calls get_frame_id (frame).  It's at this point that the frame id
for frame is computed.  Again, here's a backtrace:

    #0  compute_frame_id (fi=0xe5a760)
	at gdb/frame.c:496
    #1  0x000000000072203d in get_frame_id (fi=0xe5a760)
	at gdb/frame.c:539
    #2  0x00000000004eb50d in frame_info_to_frame_object (frame=0xe5a760)
	at gdb/python/py-frame.c:390

The test in question, dw2-dup-frame.exp, deliberately creates a broken
(cyclic) stack.  So, in this instance, the frame id for the prev
`frame' will be the same as that for `frame'.  But that particular
frame id ended up in the stash during the previous frame operation.
When, just a few lines later, we compute the frame id for `frame', the
id in question is already in the stash, thus triggering the assertion
failure.

I considered two other solutions to solving this problem:

We could prevent get_prev_frame() from being called before
get_frame_id() in frame_info_to_frame_object().  (See above for the
snippet of code where this happens.) A call to get_frame_id (frame)
could be placed ahead of that code snippet above.  I have tested this
approach and, while it does work, I can't be certain that
get_prev_frame() isn't called ahead of stashing the current frame
somewhere else in GDB, but in a less obvious way.

Another approach is to stash the current frame's id by calling
get_frame_id() in get_current_frame().  This approach is conceptually
simpler, but when importing a python unwinder, has the unwelcome side
effect of causing the unwinder to be called during import.

A cleaner looking fix would be to place this code after code
corresponding to the "Don't compute the frame id of the current frame
yet..." comment in get_prev_frame_if_no_cycle().  Sadly, this does not
work though; by the time we get to this point, the frame state for the
prev frame has been modified just enough to cause an internal error to
occur when attempting to compute the (current) frame id for inline
frames.  (The unexpected failure count increases by roughly 130
failures.)  Therefore, I decided to place it as early as possible
in get_prev_frame().

gdb/ChangeLog:

	* frame.c (get_prev_frame): Stash frame id for current frame
	prior to computing frame id for previous frame.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb/tracepoint.c: Don't use printf_vma
@ 2016-11-17  1:28 sergiodj+buildbot
  2016-11-29 11:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-17  1:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 19f1935d91bfabbe4176ffdaca95bc789b593153 ***

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

gdb/tracepoint.c: Don't use printf_vma

I noticed that bfd's printf_vma prints to stdout directly:

  bfd-in2.h:202:#define printf_vma(x) fprintf_vma(stdout,x)

This is a bad idea in gdb, where we should use
gdb_stdout/gdb_stderr/gdb_stdlog, etc., to support redirection.

Eliminate uses of sprintf_vma too while at it.

Tested on Fedora 23, w/ gdbserver.

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

	* tracepoint.c (collection_list::add_memrange): Add gdbarch
	parameter.  Use paddress instead of printf_vma.  Adjust recursive
	calls.
	(collection_list::stringify): Use paddress and phex_nz instead of
	sprintf_vma.  Adjust add_memrange call.
	* tracepoint.h (collection_list::add_memrange): Add gdbarch
	parameter.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb/ada-lang.c: one malloc -> unique_ptr<[]>
@ 2016-11-17 14:41 sergiodj+buildbot
  2016-11-29 12:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 14:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 200069c74f42ffcc726b9995a46971a86286a256 ***

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

gdb/ada-lang.c: one malloc -> unique_ptr<[]>

Switching gdb to use gnulib's C++ namespace mode reveals we're calling
malloc instead of xmalloc here:

 ..../src/gdb/ada-lang.c: In function value* ada_value_primitive_packed_val(value*, const gdb_byte*, long int, int, int, type*):
 ..../src/gdb/ada-lang.c:2592:50: error: call to malloc declared with attribute warning: The symbol ::malloc refers to the system function. Use gnulib::malloc instead. [-Werror]
	staging = (gdb_byte *) malloc (staging_len);
						   ^

We're unconditionaly using the result afterwards -- so it's not a case
of gracefully handling huge allocations.

Since we want to get rid of all cleanups, fix this by switching to
new[] and unique_ptr<[]> instead, while at it.

Regtested on Fedora 23.

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

	* ada-lang.c (ada_value_primitive_packed_val): Use unique_ptr and
	new gdb_byte[] instead of malloc and cleanups.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb/ctf.c: Get rid of mkdir redefinition
@ 2016-11-17 15:56 sergiodj+buildbot
  2016-11-29 17:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 15:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c2683c40f745397e80b6df4edf8265ecb6fd194 ***

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

gdb/ctf.c: Get rid of mkdir redefinition

Making GDB use gnulib's C++ namespace support shows this build error
on mingw:

 ../../src/gdb/ctf.c: In function 'void ctf_start(trace_file_writer*, const char*)':
 ../../src/gdb/ctf.c:309:46: error: no match for call to '(const gnulib::_gl_mkdir_wrapper) (const char*&)'
  #define mkdir(pathname, mode) mkdir (pathname)
					       ^
 ../../src/gdb/ctf.c:327:15: note: in expansion of macro 'mkdir'
    if (gnulib::mkdir (dirname, hmode) && errno != EEXIST)
		^
 ../../src/gdb/ctf.c:309:46: note: candidate: gnulib::_gl_mkdir_wrapper::type {aka int (*)(const char*, short unsigned int)} <conversion>
  #define mkdir(pathname, mode) mkdir (pathname)
					       ^
 ../../src/gdb/ctf.c:327:15: note: in expansion of macro 'mkdir'
    if (gnulib::mkdir (dirname, hmode) && errno != EEXIST)
		^
 ../../src/gdb/ctf.c:309:46: note:   candidate expects 3 arguments, 2 provided
  #define mkdir(pathname, mode) mkdir (pathname)
					       ^
 ../../src/gdb/ctf.c:327:15: note: in expansion of macro 'mkdir'
    if (gnulib::mkdir (dirname, hmode) && errno != EEXIST)
		^

The problem is the '#define mkdir ...'

Fortunately, we can just remove it, since gnulib's sys/stat.h
replacement already takes care of the Windows mkdir prototype quirk:

~~~
 /* mingw's _mkdir() function has 1 argument, but we pass 2 arguments.
    Additionally, it declares _mkdir (and depending on compile flags, an
    alias mkdir), only in the nonstandard includes <direct.h> and <io.h>,
    which are included above.  */
 # if (defined _WIN32 || defined __WIN32__) && ! defined __CYGWIN__

 #  if !GNULIB_defined_rpl_mkdir
 static int
 rpl_mkdir (char const *name, mode_t mode)
 {
   return _mkdir (name);
 }
~~~

That's sys_stat.in.h, part of the sys_stat module, which we explictly
pull in nowadays.  It wasn't being pulled when this macro was added:

  https://sourceware.org/ml/gdb-patches/2013-03/msg00736.html

That patch was partially reverted meanwhile here:

  https://sourceware.org/ml/gdb-patches/2013-12/msg00023.html

But the mkdir macro had been left behind unnoticed.

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

	* ctf.c [USE_WIN32API] (mkdir): Delete.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb/c-exp.y: fprintf -> parser_fprintf
@ 2016-11-17 16:49 sergiodj+buildbot
  2016-11-29 19:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 16:49 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

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

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Document new hard requirement on GNU make
@ 2016-11-17 18:31 sergiodj+buildbot
  2016-11-29 23:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 18:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2ff9acd32b4667ee16a03ca8d10fd8b99e22f46 ***

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

Document new hard requirement on GNU make

As discussed in [1], it would be benificial for the GDB project to start
requiring GNU make to build its software.  It would allow using useful
GNU-specific constructs, such as pattern rules.  It would also allow
removing the alternative code paths in the Makefiles (guarded by
GMAKE_TRUE/GMAKE_FALSE), simplifying the Makefile code.

[1] https://sourceware.org/ml/gdb-patches/2016-11/msg00331.html

gdb/ChangeLog:

	* NEWS: Mention requirement of GNU make.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove code that checks for GNU/non-GNU make
@ 2016-11-17 18:49 sergiodj+buildbot
  2016-11-30  3:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 18:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b165252e882c05c8217f888194877224295592d ***

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

Remove code that checks for GNU/non-GNU make

Since GNU make is now required to build GDB, we can remove everything
that checks whether the current make implemention is the GNU one or
not.  I simply removed the @GMAKE_TRUE@ prefixes and removed the whole
lines that were prefixed with @GMAKE_FALSE@.

I removed the code in the configure scripts that set those variables.

I also removed the following bits from the configure scripts:

  AC_CHECK_PROGS(MAKE, make): GNU make already defines a MAKE variable
    internally to be used when invoking Makefiles recursively.  I don't see
    this variable being used anywhere else (in scripts for example), so I
    think it's safe for removal.

  AC_PROG_MAKE_SET: This macro defines a SET_MAKE output variable, which
    is meant to be used in Makefiles to define the MAKE variable when
    using an implementation of make that doesn't already define it.
    Since we are now requiring GNU make, we don't need it anymore.
    Plus, I don't see SET_MAKE being used anywhere, so I don't think it
    was actually doing anything...

gdb/ChangeLog:

	* Makefile.in: Remove @GMAKE_TRUE@ prefixes and removes lines
	prefixed with @GMAKE_FALSE@.  Update comment related to non-GNU
	make.
	* configure.ac: Remove checks for the make program.
	* configure: Re-generate.

gdb/gdbserver/ChangeLog:

	* Makefile.in: Remove @GMAKE_TRUE@ prefixes and removes lines
	prefixed with @GMAKE_FALSE@.  Update comment related to non-GNU
	make.
	* configure.ac: Remove checks for the make program.
	* configure: Re-generate.

gdb/testsuite/ChangeLog:

	* Makefile.in: Remove @GMAKE_TRUE@ prefixes and removes lines
	prefixed with @GMAKE_FALSE@.  Update comment related to non-GNU
	make.
	* configure.ac: Remove checks for the make program.
	* configure: Re-generate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Makefile: Replace old suffix rules with pattern rules
@ 2016-11-17 19:35 sergiodj+buildbot
  2016-11-30  4:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 19:35 UTC (permalink / raw)
  To: gdb-testers

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

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

Makefile: Replace old suffix rules with pattern rules

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

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

New in v2:

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

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

gdb/ChangeLog:

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

gdb/gdbserver/ChangeLog:

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Makefile: Replace explicit subdir rules with pattern rules
@ 2016-11-17 20:10 sergiodj+buildbot
  2016-11-30  6:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 20:10 UTC (permalink / raw)
  To: gdb-testers

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

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

Makefile: Replace explicit subdir rules with pattern rules

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

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

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

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

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

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

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

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

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

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

New in v2:

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

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Help diagnose problems with the metag target when mixing static and shared binaries.
@ 2016-11-18  9:59 sergiodj+buildbot
  2016-11-30 10:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18  9:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ec49e7c0aeb6d98e379319b565aee2c89388615 ***

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

Help diagnose problems with the metag target when mixing static and shared binaries.

	PR ld/20675
	* elf32-metag.c (elf_metag_relocate_section): Replace abort with
	an informative error message.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 combined pointer authentication load instructions
@ 2016-11-18 11:23 sergiodj+buildbot
  2016-11-30 12:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 11:23 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

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

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

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

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

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

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

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

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


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 javascript floating-point conversion instruction
@ 2016-11-18 11:34 sergiodj+buildbot
  2016-11-30 16:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 11:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ccfc90a39b78b7bc4173cd9ead49d2aa59695378 ***

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

[AArch64] Add ARMv8.3 javascript floating-point conversion instruction

Add support for ARMv8.3 FJCVTZS floating-point conversion
instruction.

For details about javascript floating-point conversion see
https://community.arm.com/groups/processors/blog/2016/10/27/armv8-a-architecture-2016-additions

opcodes/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* aarch64-tbl.h (arch64_opcode_table): Add fjcvtzs.
	(QL_FP2INT_W_D, aarch64_feature_fp_v8_3, FP_V8_3): Define.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.

gas/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* testsuite/gas/aarch64/fp-armv8_3.s: Add fjcvtzs test.
	* testsuite/gas/aarch64/fp-armv8_3.d: Likewise.
	* testsuite/gas/aarch64/illegal-fjcvtzs.s: Likewise.
	* testsuite/gas/aarch64/illegal-fjcvtzs.d: Likewise.
	* testsuite/gas/aarch64/illegal-fjcvtzs.l: Likewise.
	* testsuite/gas/aarch64/illegal-nofp-armv8_3.s: Likewise.
	* testsuite/gas/aarch64/illegal-nofp-armv8_3.d: Likewise.
	* testsuite/gas/aarch64/illegal-nofp-armv8_3.l: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 weaker release consistency load instructions
@ 2016-11-18 12:49 sergiodj+buildbot
  2016-11-30 19:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 12:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28617675c264213180a599bb4327bf162029636a ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 28617675c264213180a599bb4327bf162029636a

[AArch64] Add ARMv8.3 weaker release consistency load instructions

Add support for ARMv8.3 LDAPRB, LDAPRH and LDAPR weak release
consistency load instructions. (They are equivalent to LDARB,
LDARH and LDAR instructions other than the weaker memory ordering
requirement.)

For more details about weak release consistency see
https://community.arm.com/groups/processors/blog/2016/10/27/armv8-a-architecture-2016-additions

opcodes/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* aarch64-tbl.h (arch64_opcode_table): Add ldaprb, ldaprh, ldapr.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.

gas/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* testsuite/gas/aarch64/ldst-exclusive-armv8_3.s: Add ldaprb, ldaprh, ldapr tests.
	* testsuite/gas/aarch64/ldst-exclusive-armv8_3.d: Likewise.
	* testsuite/gas/aarch64/illegal-ldapr.s: Likewise.
	* testsuite/gas/aarch64/illegal-ldapr.d: Likewise.
	* testsuite/gas/aarch64/illegal-ldapr.l: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 FCMLA and FCADD instructions
@ 2016-11-18 13:05 sergiodj+buildbot
  2016-11-30 21:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2c4ff8d52a2cd3263a547b0384692498714aa1b ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: c2c4ff8d52a2cd3263a547b0384692498714aa1b

[AArch64] Add ARMv8.3 FCMLA and FCADD instructions

Add support for FCMLA and FCADD complex arithmetic SIMD instructions.
FCMLA has an indexed element variant where the index range has to be
treated specially because a complex number takes two elements and the
indexed vector size depends on the other operands.

These complex number SIMD instructions are part of ARMv8.3
https://community.arm.com/groups/processors/blog/2016/10/27/armv8-a-architecture-2016-additions

include/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* opcode/aarch64.h (enum aarch64_opnd): Add AARCH64_OPND_IMM_ROT1,
	AARCH64_OPND_IMM_ROT2, AARCH64_OPND_IMM_ROT3.
	(enum aarch64_op): Add OP_FCMLA_ELEM.

opcodes/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* aarch64-tbl.h (QL_V3SAMEHSD_ROT, QL_ELEMENT_ROT): Define.
	(aarch64_feature_simd_v8_3, SIMD_V8_3): Define.
	(aarch64_opcode_table): Add fcmla and fcadd.
	(AARCH64_OPERANDS): Add IMM_ROT{1,2,3}.
	* aarch64-asm.h (aarch64_ins_imm_rotate): Declare.
	* aarch64-asm.c (aarch64_ins_imm_rotate): Define.
	* aarch64-dis.h (aarch64_ext_imm_rotate): Declare.
	* aarch64-dis.c (aarch64_ext_imm_rotate): Define.
	* aarch64-opc.h (enum aarch64_field_kind): Add FLD_rotate{1,2,3}.
	* aarch64-opc.c (fields): Add FLD_rotate{1,2,3}.
	(operand_general_constraint_met_p): Rotate and index range check.
	(aarch64_print_operand): Handle rotate operand.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Likewise.
	* aarch64-opc-2.c: Likewise.

gas/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* config/tc-aarch64.c (parse_operands): Handle AARCH64_OPND_IMM_ROT*.
	* testsuite/gas/aarch64/advsimd-armv8_3.d: New.
	* testsuite/gas/aarch64/advsimd-armv8_3.s: New.
	* testsuite/gas/aarch64/illegal-fcmla.s: New.
	* testsuite/gas/aarch64/illegal-fcmla.l: New.
	* testsuite/gas/aarch64/illegal-fcmla.d: New.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR c++/71696 testcase.
@ 2016-11-18 14:01 sergiodj+buildbot
  2016-12-01  0:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 14:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d2cdc86574bda0f1013be8cdc166d86b6d032bc ***

Author: Marcel Bhme <boehme.marcel@gmail.com>
Branch: master
Commit: 9d2cdc86574bda0f1013be8cdc166d86b6d032bc

PR c++/71696 testcase.

Add libiberty/testsuite/demangle-expected testcase for:

	PR c++/71696
	* cplus-dem.c: Prevent infinite recursion when there is a cycle
	in the referencing of remembered mangled types.
	(work_stuff): New stack to keep track of the remembered mangled
	types that are currently being processed.
	(push_processed_type): New method to push currently processed
	remembered type onto the stack.
	(pop_processed_type): New method to pop currently processed
	remembered type from the stack.
	(work_stuff_copy_to_from): Copy values of new variables.
	(delete_non_B_K_work_stuff): Free stack memory.
	(demangle_args): Push/Pop currently processed remembered type.
	(do_type): Do not demangle a cyclic reference and push/pop
	referenced remembered type.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Implement P0136R1, Rewording inheriting constructors.
@ 2016-11-18 16:06 sergiodj+buildbot
  2016-12-01  5:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 16:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef0f5d7cc3b2082c94beffa7c9c1a8acd8eaa427 ***

Author: Jason Merrill <jason@redhat.com>
Branch: master
Commit: ef0f5d7cc3b2082c94beffa7c9c1a8acd8eaa427

Implement P0136R1, Rewording inheriting constructors.

libiberty/
	* cp-demangle.c (d_ctor_dtor_name): Handle inheriting constructor.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] libiberty: Fix -Wimplicit-fallthrough warnings.
@ 2016-11-18 16:14 sergiodj+buildbot
  2016-12-01  9:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 16:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d17eaece8b31e642acaf4d77fe961ad8e3aaf50 ***

Author: Mark Wielaard <mjw@redhat.com>
Branch: master
Commit: 4d17eaece8b31e642acaf4d77fe961ad8e3aaf50

libiberty: Fix -Wimplicit-fallthrough warnings.

Adjust some comments, add some explicit fall through comments or explicit
returns where necessary to not get implicit-fallthrough warnings.

All fall throughs were deliberate. In one case I added an explicit return
false for clarity instead of falling through a default case (that also
would return false).

libiberty/ChangeLog:

       * cplus-dem.c (demangle_signature): Move fall through comment.
       (demangle_fund_type): Add fall through comment between 'G' and 'I'.
       * hashtab.c (iterative_hash): Add fall through comments.
       * regex.c (regex_compile): Add Fall through comment after '+'/'?'.
       (byte_re_match_2_internal): Add Fall through comment after jump_n.
       Change "Note fall through" to "Fall through".
       (common_op_match_null_string_p): Return false after set_number_at
       instead of fall through.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] libiberty: Fix memory leak in ada_demangle when symbol cannot be demangled.
@ 2016-11-18 16:19 sergiodj+buildbot
  2016-12-01  3:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aba19b625f34fb3d61263fe8044cf0c6d8804570 ***

Author: Mark Wielaard <mjw@redhat.com>
Branch: master
Commit: aba19b625f34fb3d61263fe8044cf0c6d8804570

libiberty: Fix memory leak in ada_demangle when symbol cannot be demangled.

When a symbol cannot be demangled in ada_demangle a new demangled VEC
will be allocated without deleting the demangled VEC already in use.

Running testsuite/test-demangle under valgrind will show the leak for
this entry in testsuite/demangle-expected:

    # Elaborated flag (not demangled)
    --format=gnat
    x_E
    <x_E>

 11 bytes in 1 blocks are definitely lost in loss record 1 of 1
    at 0x4C27BE3: malloc (vg_replace_malloc.c:299)
    by 0x413FE7: xmalloc (xmalloc.c:148)
    by 0x4025EC: ada_demangle (cplus-dem.c:930)
    by 0x402C59: cplus_demangle (cplus-dem.c:892)
    by 0x400FEC: main (test-demangle.c:317)

libiberty/ChangeLog:

	* cplus-dem.c (ada_demangle): Initialize demangled to NULL and
	XDELETEVEC demangled when unknown.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Implement P0012R1, Make exception specifications part of the type system.
@ 2016-11-18 16:45 sergiodj+buildbot
  2016-12-01 11:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a4ddf8dc72f0ac10c3459a91949eb1bdb07ed10d ***

Author: Jason Merrill <jason@redhat.com>
Branch: master
Commit: a4ddf8dc72f0ac10c3459a91949eb1bdb07ed10d

Implement P0012R1, Make exception specifications part of the type system.

libiberty/
	* cp-demangle.c (is_fnqual_component_type): New.
	(d_encoding, d_print_comp_inner, d_print_mod_list): Use it.
	(FNQUAL_COMPONENT_CASE): New.
	(d_make_comp, has_return_type, d_print_comp_inner)
	(d_print_function_type): Use it.
	(next_is_type_qual): New.
	(d_cv_qualifiers, d_print_mod): Handle noexcept and throw-spec.
include/
	* demangle.h (enum demangle_component_type): Add
	DEMANGLE_COMPONENT_NOEXCEPT, DEMANGLE_COMPONENT_THROW_SPEC.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] libiberty: Add -Wshadow=local to warning flags (if supported).
@ 2016-11-18 18:01 sergiodj+buildbot
  2016-12-01 15:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 18:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 59d2699cfd30f9defc454be17415c0a518ece32b ***

Author: Mark Wielaard <mark@klomp.org>
Branch: master
Commit: 59d2699cfd30f9defc454be17415c0a518ece32b

libiberty: Add -Wshadow=local to warning flags (if supported).

libiberty/ChangeLog:

       * configure.ac (ac_libiberty_warn_cflags): Add -Wshadow=local.
       * configure: Regenerated.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] libiberty: Fix some demangler crashes caused by reading past end of input.
@ 2016-11-18 18:18 sergiodj+buildbot
  2016-12-01 17:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 18:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1706852c3c6c1d39f949c933d37647d02509b9cb ***

Author: Mark Wielaard <mark@klomp.org>
Branch: master
Commit: 1706852c3c6c1d39f949c933d37647d02509b9cb

libiberty: Fix some demangler crashes caused by reading past end of input.

In various situations the cplus_demangle () function could read past the
end of input causing crashes. Add checks in various places to not advance
the demangle string location and fail early when end of string is reached.
Add various examples of input strings to the testsuite that would crash
test-demangle before the fixes.

Found by using the American Fuzzy Lop (afl) fuzzer.

libiberty/ChangeLog:

       * cplus-dem.c (demangle_signature): After 'H', template function,
       no success and don't advance position if end of string reached.
       (demangle_template): After 'z', template name, return zero on
       premature end of string.
       (gnu_special): Guard strchr against searching for zero characters.
       (do_type): If member, only advance mangled string when 'F' found.
       * testsuite/demangle-expected: Add examples of strings that could
       crash the demangler by reading past end of input.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] libiberty: Add Rust symbol demangling.
@ 2016-11-18 19:31 sergiodj+buildbot
  2016-12-01 23:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 19:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 535aade664ac4170fe82e52c9addd686156220a1 ***

Author: David Tolnay <dtolnay@gmail.com>
Branch: master
Commit: 535aade664ac4170fe82e52c9addd686156220a1

libiberty: Add Rust symbol demangling.

Adds Rust symbol demangler. Rust mangles symbols using GNU_V3 style,
adding a hash and various special character subtitutions. This adds
a new rust style to cplus_demangle and adds 3 helper functions
rust_demangle, rust_demangle_sym and rust_is_mangled.

rust-demangle.c was written by David. Mark did the code formatting to
GNU style and integration into the gcc/libiberty build system and
testsuite.

include/ChangeLog:

2016-11-03  David Tolnay <dtolnay@gmail.com>
           Mark Wielaard  <mark@klomp.org>

       * demangle.h (DMGL_RUST): New macro.
       (DMGL_STYLE_MASK): Add DMGL_RUST.
       (demangling_styles): Add dlang_rust.
       (RUST_DEMANGLING_STYLE_STRING): New macro.
       (RUST_DEMANGLING): New macro.
       (rust_demangle): New prototype.
       (rust_is_mangled): Likewise.
       (rust_demangle_sym): Likewise.

libiberty/ChangeLog:

2016-11-03  David Tolnay <dtolnay@gmail.com>
           Mark Wielaard  <mark@klomp.org>

       * Makefile.in (CFILES): Add rust-demangle.c.
       (REQUIRED_OFILES): Add rust-demangle.o.
       * cplus-dem.c (libiberty_demanglers): Add rust_demangling case.
       (cplus_demangle): Handle RUST_DEMANGLING.
       (rust_demangle): New function.
       * rust-demangle.c: New file.
       * testsuite/Makefile.in (really-check): Add check-rust-demangle.
       (check-rust-demangle): New rule.
       * testsuite/rust-demangle-expected: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] bfd: fix negative GOT offsets for non-local references on sparc64
@ 2016-11-19  0:43 sergiodj+buildbot
  2016-12-02  2:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-19  0:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc133f9f118ef4afd93da0ecba48151488c41c74 ***

Author: James Clarke <jrtc27@jrtc27.com>
Branch: master
Commit: cc133f9f118ef4afd93da0ecba48151488c41c74

bfd: fix negative GOT offsets for non-local references on sparc64

bfd/ChangeLog:

2016-11-18  James Clarke  <jrtc27@jrtc27.com>

	* elfxx-sparc.c (_bfd_sparc_elf_relocate_section): Don't convert
	R_SPARC_GOTDATA_OP_HIX22 and R_SPARC_GOTDATA_OP_LOX10 to
	R_SPARC_GOT* for non-local references. Instead, treat them like
	R_SPARC_GOTDATA_HIX22/R_SPARC_GOTDATA_LOX10 when filling in the
	immediate with the calculated relocation.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] libiberty: demangler crash with missing :? or fold expression component.
@ 2016-11-19  1:25 sergiodj+buildbot
  2016-12-01 21:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-19  1:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ddc5804ebd4b2be29ad4e3e259f5c6e907f34f26 ***

Author: Mark Wielaard <mark@klomp.org>
Branch: master
Commit: ddc5804ebd4b2be29ad4e3e259f5c6e907f34f26

libiberty: demangler crash with missing :? or fold expression component.

When constructing an :? or fold expression that requires a third
expression only the first and second were explicitly checked to
not be NULL. Since the third expression is also required in these
constructs it needs to be explicitly checked and rejected when missing.
Otherwise the demangler will crash once it tries to d_print the
NULL component. Added two examples to demangle-expected of strings
that would crash before this fix.

Found by American Fuzzy Lop (afl) fuzzer.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Makefile: fix typo
@ 2016-11-19  3:34 sergiodj+buildbot
  2016-12-02  5:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-19  3:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef787763b9495913d5be90bcdedcecb553cbf308 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: ef787763b9495913d5be90bcdedcecb553cbf308

Makefile: fix typo

Thanks to Patrick Monnerat for reporting this typo.

gdb/ChangeLog:

	* Makefile.in (%.o: $(srcdir)/gdbtk/generic/%.c): Fix typo.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Revert "bfd: allow negative offsets to _GLOBAL_OFFSET_TABLE_ in elf64 SPARC"
@ 2016-11-19 13:29 sergiodj+buildbot
  2016-12-02  8:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-19 13:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fc9967d0b28a1e037233d49cec479d3ab1e9e59 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 0fc9967d0b28a1e037233d49cec479d3ab1e9e59

Revert "bfd: allow negative offsets to _GLOBAL_OFFSET_TABLE_ in elf64 SPARC"

This reverts commit b19753ce31da347605dfa903c6fd2158e2444f0d.

As it turns out, GCC (and the assembler) needs additional work in
order to support negative GOT offsets in 64-bit sparc.  This is
breaking TLS Local Dynamic in position-independent code.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] ARI: Add detection of printf_vma and sprintf_vma
@ 2016-11-19 19:14 sergiodj+buildbot
  2016-12-02 10:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-19 19:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc188e5fd6d4f8d3061ed6c58c432a150f7966e9 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: cc188e5fd6d4f8d3061ed6c58c432a150f7966e9

ARI: Add detection of printf_vma and sprintf_vma

We shouldn't be using these, since their output goes straight to
stdout, which doesn't allow redirection. So this patch updates
the ARI to detect any such use.

gdb/ChangeLog:

        * contrib/ari/gdb_ari.sh: Add detection of printf_vma and
        sprintf_vma.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Create subobject value in pretty printer
@ 2016-11-21 14:37 sergiodj+buildbot
  2016-12-02 21:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-21 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3fff9862d5229def9318912c2de64a03dab74532 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3fff9862d5229def9318912c2de64a03dab74532

Create subobject value in pretty printer

Nowadays, we create a value of subobject in pretty printer with 'address'
being used,

  value = value_from_contents_and_address (type, valaddr + embedded_offset,
					   address + embedded_offset);

  set_value_component_location (value, val);
  /* set_value_component_location resets the address, so we may
     need to set it again.  */
  if (VALUE_LVAL (value) != lval_internalvar
      && VALUE_LVAL (value) != lval_internalvar_component
      && VALUE_LVAL (value) != lval_computed)
    set_value_address (value, address + embedded_offset);

value_from_contents_and_address creates a value from memory, but the
value we are pretty-printing may not from memory at all.

Instead of using value_from_contents_and_address, we create a value
of subobject with the same location as object's but different offset.
We avoid using address in this way.  As a result, parameter 'address'
in apply_val_pretty_printer is no longer needed, we can remove it in
next step.

We've already had the location of the 'whole' value, so it is safe
to assume we can create a value of 'component' or 'suboject' value
at the same location but with different offset.

gdb:

2016-11-21  Yao Qi  <yao.qi@linaro.org>

	* guile/scm-pretty-print.c (gdbscm_apply_val_pretty_printer):
	Don't call value_from_contents_and_address and
	set_value_address.  Call value_from_component.
	* python/py-prettyprint.c (gdbpy_apply_val_pretty_printer):
	Likewise.
	* value.c (value_from_component): New function.
	* value.h (value_from_component): Likewise.
	* valarith.c (value_subscripted_rvalue): Call
	value_from_component.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] BFD/DWARF2: Correct an `index' global shadowing error
@ 2016-11-21 17:38 sergiodj+buildbot
  2016-12-03  0:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-21 17:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6ddcd85e3c0ae1f12af60efd6d1b97ac4bfa771 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: b6ddcd85e3c0ae1f12af60efd6d1b97ac4bfa771

BFD/DWARF2: Correct an `index' global shadowing error

Fix a commit 089e3718bd8d ("Greatly improve the speed if looking up
DWARF line number information.") build regression:

cc1: warnings being treated as errors
.../bfd/dwarf2.c: In function 'build_line_info_table':
.../bfd/dwarf2.c:1614: warning: declaration of 'index' shadows a global declaration
/usr/include/string.h:304: warning: shadowed declaration is here
.../bfd/dwarf2.c: In function 'build_lookup_funcinfo_table':
.../bfd/dwarf2.c:2262: warning: declaration of 'index' shadows a global declaration
/usr/include/string.h:304: warning: shadowed declaration is here
make[4]: *** [dwarf2.lo] Error 1

in a way following commit 91d6fa6a035c ("Add -Wshadow to the gcc command
line options used when compiling the binutils.").

	bfd/
	* dwarf2.c (build_line_info_table): Rename `index' local
	variable to `line_index'.
	(build_lookup_funcinfo_table): Rename `index' local variable to
	`func_index'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add missing POSTCOMPILE step to mi/ file generation rules
@ 2016-11-21 21:38 sergiodj+buildbot
  2016-12-03  4:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-21 21:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d0de53e251ce60057d91536a4c71740b047be040 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: d0de53e251ce60057d91536a4c71740b047be040

Add missing POSTCOMPILE step to mi/ file generation rules

A little oversight from my part, it caused the Makefile not to track
the dependencies from mi/*.c files.

gdb/ChangeLog:

	* Makefile.in (%o: $(srcdir)/mi/%.c): Add missing POSTCOMPILE
	step.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use VALUE_NEXT_FRAME_ID in value_from_component
@ 2016-11-22 10:10 sergiodj+buildbot
  2016-12-03  6:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 10:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5acd8159633cfde315b01431099e1ce5b23dcf7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c5acd8159633cfde315b01431099e1ce5b23dcf7

Use VALUE_NEXT_FRAME_ID in value_from_component

We renamed VALUE_FRAME_ID to VALUE_NEXT_FRAME_ID recently,
https://sourceware.org/ml/gdb-patches/2016-11/msg00018.html
and we should use VALUE_NEXT_FRAME_ID in value_from_component
too.

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* value.c (value_from_component): Use VALUE_NEXT_FRAME_ID
	instead of VALUE_FROM_ID.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use input_bfd in relocate_section
@ 2016-11-22 10:39 sergiodj+buildbot
  2016-12-03  9:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 10:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95f0d0d2338f8eba18d2b3c8cbe15b1d584b885c ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 95f0d0d2338f8eba18d2b3c8cbe15b1d584b885c

Use input_bfd in relocate_section

It makes just a little more sense to use input_bfd when retrieving
insns for relocation, since the relocations match the endianness of
the input bfd.

	* elf32-ppc.c (ppc64_elf_relocate_section): Calculate d_offset for
	input_bfd.  Replace occurrences of output_bfd as bfd_get_32 and
	bfd_put_32 param with input_bfd.
	* elf32-ppc.c (ppc_elf_relocate_section): Likewise.  Also
	ppc_elf_vle_split16 param.
	(ppc_elf_vle_split16): Rename output_bfd param to input_bfd.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR20744, Incorrect PowerPC VLE relocs
@ 2016-11-22 11:18 sergiodj+buildbot
  2016-12-03 11:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 11:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 08dc996fedde9143cda25720961684087b133640 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 08dc996fedde9143cda25720961684087b133640

PR20744, Incorrect PowerPC VLE relocs

VLE 16A and 16D relocs were functionally swapped.

	PR 20744
include/
	* opcode/ppc.h: Define VLE insns using 16A and 16D relocs.
bfd/
	* elf32-ppc.h (struct ppc_elf_params): Add vle_reloc_fixup field.
	* elf32-ppc.c: Include opcode/ppc.h.
	(ppc_elf_howto_raw): Correct dst_mask for R_PPC_VLE_LO16A,
	R_PPC_VLE_LO16D, R_PPC_VLE_HI16A, R_PPC_VLE_HI16D, R_PPC_VLE_HA16A,
	R_PPC_VLE_HA16D, R_PPC_VLE_SDAREL_LO16A, R_PPC_VLE_SDAREL_LO16D,
	R_PPC_VLE_SDAREL_HI16A, R_PPC_VLE_SDAREL_HI16D,
	R_PPC_VLE_SDAREL_HA16A, and R_PPC_VLE_SDAREL_HA16D relocs.
	(ppc_elf_link_hash_table_create): Update default_params init.
	(ppc_elf_vle_split16): Correct shift and mask.  Add params.
	Report or fix insn/reloc mismatches.
	(ppc_elf_relocate_section): Pass input_section, offset and fixup
	to ppc_elf_vle_split16.
binutils/
	* NEWS: Mention PowerPC VLE relocation error.
gas/
	* config/tc-ppc.c: Delete VLE insn defines.
	(md_assemble): Swap use_a_reloc and use_d_reloc.
	* testsuite/gas/ppc/vle-reloc.d: Update.
ld/
	* emultempl/ppc32elf.em (params): Update initializer.  Handle
	--vle-reloc-fixup command line arg.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gas, opcodes: fix hardware capabilities bumping in the sparc assembler.
@ 2016-11-22 13:53 sergiodj+buildbot
  2016-12-03 17:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 13:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6884417a0ff3555b192d4aceeacc5e7232cad207 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 6884417a0ff3555b192d4aceeacc5e7232cad207

gas,opcodes: fix hardware capabilities bumping in the sparc assembler.

When the assembler finds an instruction which is part of a higher
opcode architecture it bumps the current opcode architecture.  For
example:

   $ echo "mwait" | as -bump
   {standard input}: Assembler messages:
   {standard input}:1: Warning: architecture bumped from "v6" to "v9m" on "mwait"

However, when two instructions pertaining to the same opcode
architecture but associated to different SPARC hardware capabilities
are found in the input stream, and no GAS architecture is specified in
the command line, the assembler bangs:

   $ echo "mwait; wr %g0,%g1,%mcdper" | as -bump
   {standard input}: Assembler messages:
   {standard input}:1: Warning: architecture bumped from "v6" to "v9m" on "mwait"
   {standard input}:1: Error: Hardware capability "sparc5" not enabled for "wr".

... and it should'nt, as WRMCDPER pertains to the same architecture
level than MWAIT.

This patch fixes this by extending the definition of sparc opcode
architectures to contain a set of hardware capabilities and making the
assembler to take these capabilities into account when updating the
set of allowed hwcaps when an architecture bump is triggered by some
instruction.

This way, hwcaps associated to architecture levels are maintained in
opcodes, while the assembler keeps the flexibiity of defining GAS
architectures including additional hwcaps (like -Asparcfmaf or the
v8plus* variants).

A test covering this failure case is included.

gas/ChangeLog:

2016-11-22  Jose E. Marchesi  <jose.marchesi@oracle.com>

       	* config/tc-sparc.c: Move HWS_* and HWS2_* definitions to
       	opcodes/sparc-opc.c.
       	(sparc_arch): Clarify the new role of the hwcap_allowed and
       	hwcap2_allowed fields.
       	(sparc_arch_table): Remove HWS_* and HWS2_* instances from
       	hwcap_allowed and hwcap2_allowed respectively.
       	(md_parse_option): Include the opcode arch hwcaps when processing
       	-A.
       	(sparc_ip): Use the current opcode arch hwcaps to update
       	hwcap_allowed, as well of the hwcaps of the instruction triggering
       	the bump.
       	* testsuite/gas/sparc/hwcaps-bump.s: New file.
       	* testsuite/gas/sparc/hwcaps-bump.l: Likewise.
       	* testsuite/gas/sparc/sparc.exp (gas_64_check): Run tests in
       	hwcaps-bump.

include/ChangeLog:

2016-11-22  Jose E. Marchesi  <jose.marchesi@oracle.com>

       	* opcode/sparc.h (sparc_opcode_arch): New fields hwcaps and
       	hwcaps2.

opcodes/ChangeLog:

2016-11-22  Jose E. Marchesi  <jose.marchesi@oracle.com>

       	* sparc-opc.c (HWS_V8): Definition moved from
       	gas/config/tc-sparc.c.
       	(HWS_V9): Likewise.
       	(HWS_VA): Likewise.
       	(HWS_VB): Likewise.
       	(HWS_VC): Likewise.
       	(HWS_VD): Likewise.
       	(HWS_VE): Likewise.
       	(HWS_VV): Likewise.
       	(HWS_VM): Likewise.
       	(HWS2_VM): Likewise.
       	(sparc_opcode_archs): Initialize hwcaps and hwcaps2 fields of
       	existing entries.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARC] Fix printing 'b' mnemonics.
@ 2016-11-22 14:50 sergiodj+buildbot
  2016-12-03 13:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 14:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4b943d7aed5edbfc31aa1e9dc9e7bcf108d76a0 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: c4b943d7aed5edbfc31aa1e9dc9e7bcf108d76a0

[ARC] Fix printing 'b' mnemonics.

gas/
2016-11-22  Claudiu Zissulescu  <claziss@synopsys.com>

	* testsuite/gas/arc/b.d: Update test result.

opcode/
2016-11-22  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-tbl.h: Reorder conditional flags with delay flags for 'b'
	instructions.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] New regcache_raw_get_signed
@ 2016-11-22 15:10 sergiodj+buildbot
  2016-12-03 21:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9fd15b2e80452f03edb3fb36c2b4c36d05f4ef4e ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9fd15b2e80452f03edb3fb36c2b4c36d05f4ef4e

New regcache_raw_get_signed

This patch adds a new regcache api regcache_raw_get_signed.

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* regcache.c (regcache_raw_get_signed): New function.
	* regcache.h (regcache_raw_get_signed): Declare.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: aarch64
@ 2016-11-22 15:55 sergiodj+buildbot
  2016-12-04  0:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 15:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0187a92f57b516f7171e70bec46701cfdaa6c6bd ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0187a92f57b516f7171e70bec46701cfdaa6c6bd

gdbarch software_single_step frame_info to regcache: aarch64

Use regcache in software_single_step.

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_software_single_step): Call
	get_regcache_arch instead of get_frame_arch.  Call
	regcache_read_pc instead of get_frame_pc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: alpha
@ 2016-11-22 16:56 sergiodj+buildbot
  2016-12-04  1:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ab2d0874025af6ee858b32c576f2461c0a1df3d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7ab2d0874025af6ee858b32c576f2461c0a1df3d

gdbarch software_single_step frame_info to regcache: alpha

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* alpha-tdep.c (alpha_deal_with_atomic_sequence): Call
	get_regcache_arch instead of get_frame_arch.  Call
	regcache_read_pc instead of get_frame_pc.
	(alpha_next_pc): Replace parameter frame with regcache.
	Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: cris
@ 2016-11-22 17:26 sergiodj+buildbot
  2016-12-04  6:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b6e2eee087cf206d5c2bf1f9523217aaf5938aa ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 5b6e2eee087cf206d5c2bf1f9523217aaf5938aa

gdbarch software_single_step frame_info to regcache: cris

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* cris-tdep.c (find_step_target): Replace parameter frame
	with regcache.  Call get_regcache_arch instead of
	get_frame_arch.  Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.
	(cris_software_single_step): Call get_regcache_arch instead
	of get_frame_arch.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: mips
@ 2016-11-22 17:49 sergiodj+buildbot
  2016-12-04  8:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 17:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7113a196bac7f1134bcdd79ad3e6badcb5d77f95 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7113a196bac7f1134bcdd79ad3e6badcb5d77f95

gdbarch software_single_step frame_info to regcache: mips

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* mips-tdep.c (mips32_bc1_pc): Replace parameter frame with
	regcache.  Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.
	(mips32_next_pc): Likewise.
	(micromips_bc1_pc): Likewise.
	(micromips_next_pc): Likewise.
	(extended_mips16_next_pc): Likewise.
	(mips16_next_pc): Likewise.
	(mips_next_pc): Likewise.
	(mips_software_single_step): Call get_regcache_arch instead
	of get_frame_arch.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: moxie
@ 2016-11-22 18:47 sergiodj+buildbot
  2016-12-04 11:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a8f341826d63a5c216c41e10bf1e4e6c3db3ce65 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: a8f341826d63a5c216c41e10bf1e4e6c3db3ce65

gdbarch software_single_step frame_info to regcache: moxie

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* moxie-tdep.c (moxie_software_single_step): Call
	get_regcache_arch instead of get_frame_arch.  Call
	regcache_read_pc instead of get_frame_pc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: nios2
@ 2016-11-22 19:25 sergiodj+buildbot
  2016-12-04 14:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3889f4909e0db5f5ca8ca043ef9825f0ad971fd6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3889f4909e0db5f5ca8ca043ef9825f0ad971fd6

gdbarch software_single_step frame_info to regcache: nios2

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* nios2-tdep.c (nios2_get_next_pc): Replace parameter frame
	with regcache.  Call regcache_raw_get_signed instead of
	get_frame_register_unsigned.
	(nios2_software_single_step): Call get_regcache_arch
	instead of get_frame_arch.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: sparc
@ 2016-11-22 20:15 sergiodj+buildbot
  2016-12-04 17:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd76b525eda02c30c4412698a2ff309b975d417a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: cd76b525eda02c30c4412698a2ff309b975d417a

gdbarch software_single_step frame_info to regcache: sparc

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* sparc-tdep.c (sparc_analyze_control_transfer): Replace parameter
	frame with regcache.  Call get_current_frame.
	(sparc_software_single_step): Call get_regcache_arch instead of
	get_frame_arch.  Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: s390
@ 2016-11-22 20:47 sergiodj+buildbot
  2016-12-04 22:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 20:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad76968956f30bed6d120e0dfd247034e0855fea ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ad76968956f30bed6d120e0dfd247034e0855fea

gdbarch software_single_step frame_info to regcache: s390

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* s390-linux-tdep.c (s390_software_single_step): Call
	get_regcache_arch instead of get_frame_arch.  Call
	regcache_read_pc instead of get_frame_pc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: rs6000
@ 2016-11-22 21:00 sergiodj+buildbot
  2016-12-05  2:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41e26ad32d17ee35f79f629654811f5e8656cab8 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 41e26ad32d17ee35f79f629654811f5e8656cab8

gdbarch software_single_step frame_info to regcache: rs6000

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* rs6000-aix-tdep.c (branch_dest): Replace parameter frame with
	regcache.  Call get_regcache_arch instead of get_frame_arch.
	Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.
	(rs6000_software_single_step): Likewise.
	* rs6000-tdep.c (ppc_deal_with_atomic_sequence): Call
	get_regcache_arch instead of get_frame_arch.  Call
	regcache_read_pc instead of get_frame_pc.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: spu
@ 2016-11-22 22:40 sergiodj+buildbot
  2016-12-05  4:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 22:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2260160f8cde8de118914ddeaf797bea42e65ce ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: b2260160f8cde8de118914ddeaf797bea42e65ce

gdbarch software_single_step frame_info to regcache: spu

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* spu-tdep.c (spu_software_single_step): Call get_regcache_arch
	instead of get_frame_arch.  Call regcache_read_pc instead of
	get_frame_pc.  Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Change gdbarch software_single_step frame_info to regcache
@ 2016-11-23  0:03 sergiodj+buildbot
  2016-12-05  6:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  0:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5ea389ac78ccd7c426a93f43e6117dad9ce0878 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f5ea389ac78ccd7c426a93f43e6117dad9ce0878

Change gdbarch software_single_step frame_info to regcache

This patch changes gdbarch method software_single_step's parameter from
"struct frame_info *" to "struct regcache *, IOW, software_single_step
starts to use current regcache rather than current frame for software
single.

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* gdbarch.sh (software_single_step): Change parameter from frame_info
	to regcache.
	* gdbarch.c, gdbarch.h: Regenerated.
	* aarch64-tdep.c (aarch64_software_single_step): Change parameter
	from frame_info to regcache.  Don't call get_current_regcache.
	* alpha-tdep.c (alpha_deal_with_atomic_sequence): Likewise.
	(alpha_software_single_step): Likewise.
	* alpha-tdep.h (alpha_software_single_step): Update declaration.
	* arm-linux-tdep.c (arm_linux_software_single_step): Likewise.
	* arm-tdep.c (arm_software_single_step): Likewise.
	* arm-tdep.h (arm_software_single_step): Likewise.
	* breakpoint.c (insert_single_step_breakpoint): Pass regcache to
	gdbarch_software_single_step.
	* cris-tdep.c (cris_software_single_step): Change parameter from
	frame_info to regcache.  Don't call get_current_regcache.
	* mips-tdep.c (mips_software_single_step): Likewise.
	* mips-tdep.h (mips_software_single_step): Update declaration.
	* moxie-tdep.c (moxie_software_single_step): Likewise.
	* nios2-tdep.c (nios2_software_single_step): Likewise.
	* ppc-tdep.h (ppc_deal_with_atomic_sequence): Update declaration.
	* rs6000-aix-tdep.c (rs6000_software_single_step): Likewise.
	* rs6000-tdep.c (ppc_deal_with_atomic_sequence): Likewise.
	* s390-linux-tdep.c (s390_software_single_step): Likewise.
	* sparc-tdep.c (sparc_software_single_step): Likewise.
	* spu-tdep.c (spu_software_single_step): Likewise.
	* tic6x-tdep.c (tic6x_software_single_step): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: tic6x
@ 2016-11-23  0:36 sergiodj+buildbot
  2016-12-05  2:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  0:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb090cfa157e35fac1c10c062fd005e38b894ea4 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: fb090cfa157e35fac1c10c062fd005e38b894ea4

gdbarch software_single_step frame_info to regcache: tic6x

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* tic6x-tdep.c (tic6x_condition_true): Replace frame with
	regcache.  Call regcache_raw_get_signed instead of
	get_frame_register_signed.
	(tic6x_get_next_pc): Likewise.  Caller updated.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix spelling mistakes in comments in shell scripts
@ 2016-11-23  1:00 sergiodj+buildbot
  2016-12-05 12:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  1:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca3cbe5cd7715d1559d55f8e71be1dd7340f13b1 ***

Author: Ambrogino Modigliani <ambrogino.modigliani@gmail.com>
Branch: master
Commit: ca3cbe5cd7715d1559d55f8e71be1dd7340f13b1

Fix spelling mistakes in comments in shell scripts

gdb/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * contrib/expect-read1.sh: Fix spelling in comments.
        * gdb_buildall.sh: Fix spelling in comments.
        * gdb_mbuild.sh: Fix spelling in comments.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbserver: Use debug_printf for debug output
@ 2016-11-23  1:51 sergiodj+buildbot
  2016-12-05 15:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  1:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4eefa7bcf286b879f61b9e1ec1c97230f5345104 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4eefa7bcf286b879f61b9e1ec1c97230f5345104

gdbserver: Use debug_printf for debug output

gdb/gdbserver/ChangeLog:
2016-11-23  Pedro Alves  <palves@redhat.com>

	* linux-low.c (check_zombie_leaders): Use debug_printf for debug
	output.
	* notif.c (handle_notif_ack, notif_event_enque): Likewise.
	* remote-utils.c (putpkt_binary_1, readchar, getpkt): Use
	debug_printf and debug_flush for debug output.
	* server.c (handle_general_set): Likewise.
	* thread-db.c (try_thread_db_load): Use debug_printf for debug
	output.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbserver: Use warning for warnings
@ 2016-11-23  2:43 sergiodj+buildbot
  2016-12-05 18:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  2:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9986ba08876f86f7d36d230afc11b60a34287da8 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 9986ba08876f86f7d36d230afc11b60a34287da8

gdbserver: Use warning for warnings

gdb/gdbserver/ChangeLog:
2016-11-23  Pedro Alves  <palves@redhat.com>

	* event-loop.c (handle_file_event): Use warning.
	* linux-low.c (linux_resume_one_lwp_throw): Use warning.
	* mem-break.c (add_breakpoint_condition, add_breakpoint_commands):
	Use warning.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix spelling mistakes in comments in configure scripts
@ 2016-11-23  3:21 sergiodj+buildbot
  2016-12-05 11:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  3:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96fe45624e51f1bb747e36cf8bdaab216f31c5ec ***

Author: Ambrogino Modigliani <ambrogino.modigliani@gmail.com>
Branch: master
Commit: 96fe45624e51f1bb747e36cf8bdaab216f31c5ec

Fix spelling mistakes in comments in configure scripts

All changes are limited to comments, and no run-time behavior is
affected.

bfd/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * warning.m4: Fix spelling in comments.
        * configure.ac: Fix spelling in comments.
        * configure: Regenerate.

binutils/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * configure: Regenerate.

gdb/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * configure.ac: Fix spelling in comments.
        * configure: Regenerate.

gas/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * configure: Regenerate.

gold/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * configure: Regenerate.

gprof/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * configure: Regenerate.

ld/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * configure: Regenerate.

opcodes/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Regen POTFILES.in
@ 2016-11-23  7:46 sergiodj+buildbot
  2016-12-05 22:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  7:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ae0486cdce5d2ed4c922c598a3258fcbd9c8f29 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 3ae0486cdce5d2ed4c922c598a3258fcbd9c8f29

Regen POTFILES.in

bfd/
	* po/BLD-POTFILES.in: Regenerate.
	* po/SRC-POTFILES.in: Regenerate.
gas/
	* po/POTFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Delete duplicate target short-cuts to dynamic sections
@ 2016-11-23  8:40 sergiodj+buildbot
  2016-12-06  1:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  8:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce558b89b15a18fd67fdc02a4d410a6d92d2ba63 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: ce558b89b15a18fd67fdc02a4d410a6d92d2ba63

Delete duplicate target short-cuts to dynamic sections

We'd like to have the elf_link_hash_table srelplt field rather than
some private target field used to save short-cuts to a PLT relocation
section.  This save a little space but mainly is so that the generic
ELF code can access the field.  Ditto for other dynamic sections.

	* elf-m10300.c (mn10300_elf_check_relocs): Use elf htab shortcuts
	to dynamic sections.
	(mn10300_elf_final_link_relocate): Likewise.
	(_bfd_mn10300_elf_adjust_dynamic_symbol): Likewise.
	(_bfd_mn10300_elf_size_dynamic_sections): Likewise.
	(_bfd_mn10300_elf_finish_dynamic_symbol): Likewise.
	(_bfd_mn10300_elf_finish_dynamic_sections): Likewise.
	* elf32-bfin.c (bfin_check_relocs): Likewise.
	(bfin_relocate_section): Likewise.
	(bfin_gc_sweep_hook): Likewise.
	(struct bfinfdpic_elf_link_hash_table): Delete sgot, sgotrel, splt
	and spltrel.
	(bfinfdpic_got_section, bfinfdpic_gotrel_section,
	bfinfdpic_plt_section, bfinfdpic_pltrel_section): Define using elf
	shortcut sections.
	(_bfin_create_got_section): Use elf htab shortcuts to dyn sections.
	Delete dead code.
	(bfin_finish_dynamic_symbol): Use elf htab shortcuts to dyn sections.
	(bfin_size_dynamic_sections): Likewise.
	* elf32-cr16.c (_bfd_cr16_elf_create_got_section): Likewise.
	(cr16_elf_check_relocs): Likewise.
	(cr16_elf_final_link_relocate): Likewise.
	(_bfd_cr16_elf_create_dynamic_sections): Likewise.
	(_bfd_cr16_elf_adjust_dynamic_symbol): Likewise.
	(_bfd_cr16_elf_size_dynamic_sections): Likewise.
	(_bfd_cr16_elf_finish_dynamic_symbol): Likewise.
	(_bfd_cr16_elf_finish_dynamic_sections): Likewise.
	* elf32-cris.c (cris_elf_relocate_section): Likewise.
	(elf_cris_finish_dynamic_symbol): Likewise.
	(elf_cris_finish_dynamic_sections): Likewise.
	(cris_elf_gc_sweep_hook): Likewise.
	(elf_cris_adjust_gotplt_to_got): Likewise.
	(elf_cris_adjust_dynamic_symbol): Likewise.
	(cris_elf_check_relocs): Likewise.  Delete dead code.
	(elf_cris_size_dynamic_sections): Use elf htab shortcuts to dynamic
	sections.
	(elf_cris_discard_excess_program_dynamics): Likewise.
	* elf32-frv.c (struct frvfdpic_elf_link_hash_table): Delete sgot,
	sgotrel, splt and spltrel.
	(frvfdpic_got_section, frvfdpic_gotrel_section,
	frvfdpic_plt_section, frvfdpic_pltrel_section): Define using elf
	shortcut sections.
	(_frv_create_got_section): Likewise.
	* elf32-hppa.c (struct elf32_hppa_link_hash_table): Delete sgot,
	srelgot, splt and srelplt.
	(hppa_build_one_stub): Use elf htab shortcuts to dynamic sections.
	(elf32_hppa_create_dynamic_sections): Likewise.
	(elf32_hppa_check_relocs): Likewise.
	(allocate_plt_static): Likewise.
	(allocate_dynrelocs): Likewise.
	(elf32_hppa_size_dynamic_sections): Likewise.
	(elf32_hppa_relocate_section): Likewise.
	(elf32_hppa_finish_dynamic_symbol): Likewise.
	(elf32_hppa_finish_dynamic_sections): Likewise.
	* elf32-i370.c (i370_elf_finish_dynamic_sections): Likewise.
	* elf32-lm32.c (struct elf_lm32_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	(lm32fdpic_got_section, lm32fdpic_gotrel_section): Define using elf
	shortcut sections.
	(create_got_section): Delete.  Use _bfd_elf_create_got_section instead.
	(lm32_elf_relocate_section): Use elf htab shortcuts to dyn sections.
	(lm32_elf_check_relocs): Likewise.
	(lm32_elf_finish_dynamic_sections): Likewise.
	(lm32_elf_finish_dynamic_symbol): Likewise.
	(allocate_dynrelocs): Likewise.
	(lm32_elf_size_dynamic_sections): Likewise.
	(lm32_elf_create_dynamic_sections): Likewise.
	* elf32-m32c.c (m32c_elf_relocate_section): Likewise.
	(m32c_elf_check_relocs): Likewise.
	(m32c_elf_finish_dynamic_sections): Likewise.
	(m32c_elf_always_size_sections): Likewise.
	* elf32-m32r.c (struct elf_m32r_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	(create_got_section): Delete.  Use _bfd_elf_create_got_section instead.
	(m32r_elf_create_dynamic_sections): Use elf htab shortcuts to dynamic
	sections.
	(allocate_dynrelocs): Likewise.
	(m32r_elf_size_dynamic_sections): Likewise.
	(m32r_elf_relocate_section): Likewise.
	(m32r_elf_finish_dynamic_symbol): Likewise.
	(m32r_elf_finish_dynamic_sections): Likewise.
	(m32r_elf_check_relocs): Likewise.
	* elf32-m68k.c (elf_m68k_partition_multi_got): Likewise.
	(elf_m68k_check_relocs): Likewise.
	(elf_m68k_adjust_dynamic_symbol): Likewise.
	(elf_m68k_size_dynamic_sections): Likewise.
	(elf_m68k_relocate_section): Likewise.
	(elf_m68k_finish_dynamic_symbol): Likewise.
	(elf_m68k_finish_dynamic_sections): Likewise.
	* elf32-metag.c (struct elf_metag_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	(elf_metag_relocate_section): Use elf htab shortcuts to dynamic
	sections.
	(elf_metag_create_dynamic_sections): Likewise.  Allocate got header
	here in .got.
	(elf_metag_check_relocs): Use elf htab shortcuts to dynamic sections.
	(allocate_dynrelocs): Likewise.
	(elf_metag_size_dynamic_sections): Likewise.
	(elf_metag_finish_dynamic_symbol): Likewise.
	(elf_metag_finish_dynamic_sections): Likewise.
	(elf_metag_size_stubs): Likewise.
	(elf_backend_got_header_size): Don't define.
	(elf_backend_want_got_plt): Define.
	* elf32-microblaze.c (struct elf32_mb_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelpl.
	(microblaze_elf_relocate_section): Use elf htab shortcuts to dynamic
	sections.
	(create_got_section): Delete.  Use _bfd_elf_create_got_section instead.
	(microblaze_elf_check_relocs): Use elf htab shortcuts to dyn sections.
	(microblaze_elf_create_dynamic_sections): Likewise.
	(allocate_dynrelocs): Likewise.
	(microblaze_elf_size_dynamic_sections): Likewise.
	(microblaze_elf_finish_dynamic_symbol): Likewise.
	(microblaze_elf_finish_dynamic_sections): Likewise.
	* elf32-nds32.c (nds32_elf_link_hash_table_create): Don't NULL
	already zero fields.
	(create_got_section): Delete.  Use _bfd_elf_create_got_section instead.
	(nds32_elf_create_dynamic_sections): Use elf htab shortcuts to dynamic
	sections.
	(allocate_dynrelocs): Likewise.
	(nds32_elf_size_dynamic_sections): Likewise.
	(nds32_elf_relocate_section): Likewise.
	(nds32_elf_finish_dynamic_symbol): Likewise.
	(nds32_elf_finish_dynamic_sections): Likewise.
	(nds32_elf_check_relocs): Likewise.
	(calculate_plt_memory_address): Likewise.
	(calculate_got_memory_address): Likewise.
	* elf32-nds32.h (struct elf_nds32_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	* elf32-or1k.c (struct elf_or1k_link_hash_table): Likewise.
	(or1k_elf_relocate_section): Use elf htab shortcuts to dyn sections.
	(create_got_section): Delete.  Use _bfd_elf_create_got_section instead.
	(or1k_elf_check_relocs): Use elf htab shortcuts to dynamic sections.
	(or1k_elf_finish_dynamic_sections): Likewise.
	(or1k_elf_finish_dynamic_symbol): Likewise.
	(allocate_dynrelocs): Likewise.
	(or1k_elf_size_dynamic_sections): Likewise.
	(or1k_elf_create_dynamic_sections): Likewise.
	* elf32-ppc.c (struct ppc_elf_link_hash_table): Delete got, relgot,
	plt, relplt, iplt, reliplt and sgotplt.
	(ppc_elf_create_got): Use elf htab shortcuts to dynamic sections.
	(ppc_elf_create_glink): Likewise.
	(ppc_elf_create_dynamic_sections): Likewise.
	(ppc_elf_check_relocs): Likewise.
	(ppc_elf_select_plt_layout): Likewise.
	(ppc_elf_tls_setup): Likewise.
	(allocate_got): Likewise.
	(allocate_dynrelocs): Likewise.
	(ppc_elf_size_dynamic_sections): Likewise.
	(ppc_elf_relax_section): Likewise.
	(ppc_elf_relocate_section): Likewise.
	(ppc_elf_finish_dynamic_symbol): Likewise.
	(ppc_elf_reloc_type_class): Likewise.
	(ppc_elf_finish_dynamic_sections): Likewise.
	* elf32-rl78.c (rl78_elf_relocate_section): Likewise.
	(rl78_elf_check_relocs): Likewise.
	(rl78_elf_finish_dynamic_sections): Likewise.
	(rl78_elf_always_size_sections): Likewise.
	* elf32-s390.c 	(create_got_section): Delete.
	(elf_s390_create_dynamic_sections): Use _bfd_elf_create_got_section.
	(elf_s390_check_relocs): Likewise.
	* elf32-score.c (score_elf_create_got_section): Set elf shortcuts.
	(s3_bfd_score_elf_finish_dynamic_sections): Use elf shortcuts.
	* elf32-score7.c (score_elf_create_got_section): As above.
	(s7_bfd_score_elf_finish_dynamic_sections): As above.
	* elf32-sh.c (struct elf_sh_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	(create_got_section): Don't set them.
	(sh_elf_create_dynamic_sections): Use elf htab shortcuts to dynamic
	sections.
	(allocate_dynrelocs): Likewise.
	(sh_elf_size_dynamic_sections): Likewise.
	(sh_elf_add_rofixup): Likewise.
	(sh_elf_relocate_section): Likewise.
	(sh_elf_check_relocs): Likewise.
	(sh_elf_finish_dynamic_symbol): Likewise.
	(sh_elf_finish_dynamic_sections): Likewise.
	* elf32-tic6x.c (elf32_tic6x_finish_dynamic_symbol): Likewise.
	* elf32-tilepro.c (tilepro_elf_create_got_section): Likewise.
	* elf32-vax.c (elf_vax_check_relocs): Likewise.
	(elf_vax_adjust_dynamic_symbol): Likewise.
	(elf_vax_always_size_sections): Likewise.
	(elf_vax_instantiate_got_entries): Likewise.
	(elf_vax_relocate_section): Likewise.
	(elf_vax_finish_dynamic_symbol): Likewise.
	(elf_vax_finish_dynamic_sections): Likewise.
	* elf32-xstormy16.c (xstormy16_elf_check_relocs): Likewise.
	(xstormy16_elf_always_size_sections): Likewise.
	(xstormy16_elf_relocate_section): Likewise.
	(xstormy16_elf_finish_dynamic_sections): Likewise.
	* elf32-xtensa.c (struct elf_xtensa_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	(elf_xtensa_create_dynamic_sections): Use elf htab shortcuts to
	dynamic sections.
	(elf_xtensa_allocate_dynrelocs): Likewise.
	(elf_xtensa_allocate_local_got_size): Likewise.
	(elf_xtensa_size_dynamic_sections): Likewise.
	(elf_xtensa_relocate_section): Likewise.
	(elf_xtensa_finish_dynamic_sections): Likewise.
	(shrink_dynamic_reloc_sections): Likewise.
	(elf_xtensa_get_plt_section): Likewise.
	(elf_xtensa_get_gotplt_section): Likewise.
	(xtensa_callback_required_dependence): Likewise.
	* elf64-alpha.c (elf64_alpha_create_dynamic_sections): Set elf htab
	shortcuts to dynamic sections.
	(elf64_alpha_adjust_dynamic_symbol): Use elf htab shortcuts to
	dynamic sections.
	(elf64_alpha_size_plt_section): Likewise.
	(elf64_alpha_size_rela_got_1): Likewise.
	(elf64_alpha_size_rela_got_section): Likewise.
	(elf64_alpha_relocate_section): Likewise.
	(elf64_alpha_finish_dynamic_symbol): Likewise.
	(elf64_alpha_finish_dynamic_sections): Likewise.
	* elf64-hppa.c (elf64_hppa_size_dynamic_sections): Likewise.
	* elf64-s390.c (create_got_section): Delete.
	(elf_s390_create_dynamic_sections): Use _bfd_elf_create_got_section.
	(elf_s390_check_relocs): Likewise.
	* elf64-sh64.c (sh_elf64_relocate_section): Use elf htab shortcuts to
	dynamic sections.
	(sh_elf64_check_relocs): Likewise.
	(sh64_elf64_adjust_dynamic_symbol): Likewise.
	(sh64_elf64_size_dynamic_sections): Likewise.
	(sh64_elf64_finish_dynamic_symbol): Likewise.
	(sh64_elf64_finish_dynamic_sections): Likewise.
	* elflink.c (_bfd_elf_create_got_section): Likewise.
	* elfnn-aarch64.c (aarch64_elf_create_got_section): Likewise.
	* elfnn-ia64.c (elfNN_ia64_size_dynamic_sections): Likewise.
	(elfNN_ia64_finish_dynamic_sections): Likewise.
	* elfnn-riscv.c (riscv_elf_create_got_section): Likewise.
	* elfxx-mips.c (struct mips_elf_link_hash_table): Delete srellt,
	sgotplt, splt and sgot.
	(mips_elf_initialize_tls_slots): Use elf htab shortcuts to dynamic
	sections.
	(mips_elf_gotplt_index): Likewise.
	(mips_elf_primary_global_got_index): Likewise.
	(mips_elf_global_got_index): Likewise.
	(mips_elf_got_offset_from_index): Likewise.
	(mips_elf_create_local_got_entry): Likewise.
	(mips_elf_create_got_section): Likewise.
	(mips_elf_calculate_relocation): Likewise.
	(_bfd_mips_elf_create_dynamic_sections): Likewise.
	(_bfd_mips_elf_adjust_dynamic_symbol): Likewise.
	(mips_elf_lay_out_got): Likewise.
	(mips_elf_set_plt_sym_value): Likewise.
	(_bfd_mips_elf_size_dynamic_sections): Likewise.
	(_bfd_mips_elf_finish_dynamic_symbol): Likewise.
	(_bfd_mips_vxworks_finish_dynamic_symbol): Likewise.
	(mips_finish_exec_plt): Likewise.
	(mips_vxworks_finish_exec_plt): Likewise.
	(mips_vxworks_finish_shared_plt): Likewise.
	(_bfd_mips_elf_finish_dynamic_sections): Likewise.
	* elfxx-sparc.c (sparc_finish_dyn): Likewise.
	* elfxx-tilegx.c (tilegx_elf_create_got_section): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] elf_backend_dtrel_excludes_plt
@ 2016-11-23  9:06 sergiodj+buildbot
  2016-12-06  5:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  9:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64f52338e924cce3a205527136e145da660a4686 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 64f52338e924cce3a205527136e145da660a4686

elf_backend_dtrel_excludes_plt

Now that all targets creating .rel.plt/.rela.plt use the ELF hash
table shortcut srelplt, the generic ELF code can set up DT_RELSZ/
DT_RELASZ and DT_REL/DT_RELA for targets that don't want PLT relocs
included in those tags.

	* elf-bfd.h (struct elf_backend_data): Add dtrel_excludes_plt.
	* elfxx-target.h (elf_backend_dtrel_excludes_plt): Define.
	(elfNN_bed): Init new field.
	* elflink.c (bfd_elf_final_link): Add and use htab variable.  Handle
	dtrel_excludes_plt.
	* elf-m10300.c (_bfd_mn10300_elf_finish_dynamic_sections): Delete
	DT_RELASZ code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-arc.c (elf_arc_finish_dynamic_sections): Delete DT_RELASZ code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-arm.c (elf32_arm_finish_dynamic_sections): Delete code
	subtracting off plt relocs from DT_RELSZ, DT_RELASZ.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-cr16.c (_bfd_cr16_elf_finish_dynamic_sections): Delete
	DT_RELASZ code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-cris.c (elf_cris_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-hppa.c (elf32_hppa_finish_dynamic_sections): Delete DT_RELASZ
	and DT_RELA code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-i386.c (elf_i386_finish_dynamic_sections): Delete DT_RELSZ
	and DT_REL code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-lm32.c (lm32_elf_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-m32r.c (m32r_elf_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-m68k.c (elf_m68k_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-metag.c (elf_metag_finish_dynamic_sections): Delete DT_RELASZ
	and DT_RELA code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-microblaze.c (microblaze_elf_finish_dynamic_sections): Delete
	DT_RELASZ and DT_RELA code.  Use ELF htab shortcuts for other
	dynamic sections.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-mips.c (elf_backend_dtrel_excludes_plt): Define.
	* elf32-nds32.c (nds32_elf_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-nios2.c (nios2_elf32_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-or1k.c (or1k_elf_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-ppc.c (ppc_elf_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-sh.c (sh_elf_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-sparc.c (elf_backend_dtrel_excludes_plt): Define.
	* elf32-vax.c (elf_vax_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf32-xtensa.c (elf_xtensa_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf64-alpha.c (elf64_alpha_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf64-ppc.c (ppc64_elf_finish_dynamic_sections): Delete DT_RELASZ
	and DT_RELA code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf64-sh64.c (sh64_elf64_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elf64-x86-64.c (elf_x86_64_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elfnn-aarch64.c (elfNN_aarch64_finish_dynamic_sections): Delete
	DT_RELASZ code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elfnn-ia64.c (elfNN_ia64_finish_dynamic_sections): Delete DT_RELASZ
	code.
	(elf_backend_dtrel_excludes_plt): Define.
	* elfxx-mips.c (_bfd_mips_elf_finish_dynamic_sections): Delete
	DT_RELASZ code.
	* elfxx-sparc.c (sparc_finish_dyn): Delete DT_RELASZ code.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix the linker so that it will not silently generate ELF binaries with invalid program headers. Fix readelf to report such invalid binaries.
@ 2016-11-23 11:55 sergiodj+buildbot
  2016-12-06  6:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a9ccd70f9a75dc6b48d340059f28ef3550c107b ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 1a9ccd70f9a75dc6b48d340059f28ef3550c107b

Fix the linker so that it will not silently generate ELF binaries with invalid program headers.  Fix readelf to report such invalid binaries.

	PR ld/20815
bfd	* elf.c (elf_modify_segment_map): Allow empty LOAD segments if
	they contain the program headers.
	(_bfd_elf_map_sections_to_segments): If the linker created the
	PHDR segment then always attempt to include it in a LOAD segment.
	(assign_file_positions_for_non_load_sections): Allow LOAD segments
	to overlap PHDR segments.
	(phdr_sorter): New function.  Sorts program headers.
	(assign_file_positions_except_relocs): Sort the program headers
	before writing them out.  Issue an error if the PHDR segment is
	not covered by a LOAD segment, unless the backend allows it.
	* elf-bfd.h (struct elf_backend_data): Add
	elf_backend_allow_non_load_phdr.
	* elfxx-target.h (elf_backend_allow_non_load_phdr): Provide
	default definition that returns FALSE.
	(elfNN_bed): Initialise the elf_backend_allow_non_load_phdr
	field.
	* elf64-hppa.c (elf64_hppa_allow_non_load_phdr): New function.
	Returns TRUE.
	(elf_backend_allow_non_load_phdr): Define.
	* elf-m10300.c (_bfd_mn10300_elf_size_dynamic_sections): Do not
	place the interpreter string into the .interp section if the
	nointerp flag is set in the link info structure.
	* elf32-arc.c (elf_arc_size_dynamic_sections): Likewise.
	* elf32-score7.c (score_elf_final_link_relocate): Allow for the
	_gp symbol not being part of the output.

binutils* readelf.c (process_program_headers): Check PT_LOAD and PT_PHDR
	segments for validity.

ld	* ld.texinfo: Note that PT_TLS can be used as a segment type.
	* testsuite/ld-discard/discard.ld: Add space for program headers.
	* testsuite/ld-elf/flags1.ld: Likewise.
	* testsuite/ld-elf/maxpage3.t: Likewise.
	* testsuite/ld-elf/noload-1.t: Likewise.
	* testsuite/ld-elf/orphan.ld: Likewise.
	* testsuite/ld-elf/overlay.t: Likewise.
	* testsuite/ld-elf/pr14052.t: Likewise.
	* testsuite/ld-elf/pr19539.t: Likewise.
	* testsuite/ld-elf/provide-hidden-1.ld: Likewise.
	* testsuite/ld-elf/provide-hidden-s.ld: Likewise.
	* testsuite/ld-elf/weak-dyn-1.ld: Likewise.
	* testsuite/ld-i386/pr19539.t: Likewise.
	* testsuite/ld-scripts/defined.t: Likewise.
	* testsuite/ld-scripts/defined6.t: Likewise.
	* testsuite/ld-scripts/dynamic-sections.t: Likewise.
	* testsuite/ld-scripts/empty-aligned.t: Likewise.
	* testsuite/ld-scripts/provide-2.t: Likewise.
	* testsuite/ld-scripts/provide-4.t: Likewise.
	* testsuite/ld-vax-elf/plt-local.ld: Likewise.
	* testsuite/ld-x86-64/pr19539.t: Likewise.
	* testsuite/ld-elf/ehdr_start-missing.d: Do not initialise the
	dynamic linker.
	* testsuite/ld-elf/ehdr_start-weak.d: Likewise.
	* testsuite/ld-elf/elf.exp (pr14170, pr17068): Likewise.
	* testsuite/ld-elf/loadaddr1.d: Update expected readelf output.
	* testsuite/ld-elf/noload-2.d: Likewise.
	* testsuite/ld-powerpc/vxworks2.sd: Likewise.
	* testsuite/ld-scripts/phdrs3a.d: Likewise.
	* testsuite/ld-scripts/size-2.d: Likewise.
	* testsuite/ld-elf/group.ld: Add program headers.
	* testsuite/ld-elf/overlay.d: Skip for SPU.
	* testsuite/ld-elf/flags1.d: Skip for RX.
	* testsuite/ld-elf/pr19162.d: Skip for HPPA64.
	* testsuite/ld-elf/pr19539.d: Skip for ALPHA.
	* testsuite/ld-scripts/empty-orphan.t: Update program headers.
	* testsuite/ld-scripts/size-2.t: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Makefiles: Flatten and sort file lists
@ 2016-11-23 15:19 sergiodj+buildbot
  2016-12-06 10:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b593ecca856860a8b38deb808493bba4beef3aee ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: b593ecca856860a8b38deb808493bba4beef3aee

Makefiles: Flatten and sort file lists

I find the big file lists in the Makefiles a bit ugly and not very
practical.  Since there are multiple filenames on each line (as much as
fits in 80 columns), it's not easy to add, remove or change a name in
the middle.  As a result, we have a mix of long and short lines in no
particular order (ALL_TARGET_OBS is a good example).

I therefore suggest flattening the lists (one name per line) and keeping
them in alphabetical order.  The diffs will be much clearer and merge
conflicts will be easier to resolve.

A nice (IMO) side-effect I observed is that the files are compiled
alphabetically by make, so it gives a rough idea of the progress of the
build.

I added a comment in gdb/Makefile.in to mention to keep the file lists
ordered, and gave the general guidelines on what order to respect.  I
added a comment in other Makefiles which refers to gdb/Makefile.in, to
avoid duplication.

Running the patch through the buildbot found that gdb.base/default.exp
started to fail.  The languages in the error message shown when typing
"set language" have changed order.  We could probably improve gdb so
that it prints them in a stable order, regardless of the order of the
object list passed to the linked, but just fixing the test is easier for
now.

New in v2:

 - Change ordering style, directories go at the end.
 - Cleanup gdbserver's and data-directory's Makefile as well.
 - Add comments at top of Makefiles about the ordering.
 - Remove wrong trailing backslahes.
 - Fix test gdb.base/default.exp.

gdb/ChangeLog:

	* Makefile.in: Add comment about file lists ordering.
	(SUBDIR_CLI_OBS, SUBDIR_CLI_SRCS, SUBDIR_MI_OBS, SUBDIR_MI_SRCS,
	SUBDIR_TUI_OBS, SUBDIR_TUI_SRCS, SUBDIR_GCC_COMPILE_OBS,
	SUBDIR_GCC_COMPILE_SRCS, SUBDIR_GUILE_OBS, SUBDIR_GUILE_SRCS,
	SUBDIR_PYTHON_OBS, SUBDIR_PYTHON_SRCS, SUBDIR_GDBTK_OBS,
	SUBDIR_GDBTK_SRCS, XMLFILES, REMOTE_OBS, ALL_64_TARGET_OBS,
	ALL_TARGET_OBS, SFILES, HFILES_NO_SRCDIR, HFILES_WITH_SRCDIR,
	COMMON_OBS, YYFILES, YYOBJ, generated_files, ALLDEPFILES):
	Flatten list and order alphabetically.
	* data-directory/Makefile.in: Add comment about file lists
	ordering.
	(GEN_SYSCALLS_FILES, PYTHON_FILE_LIST): Flatten list and order
	alphabetically.

gdb/gdbserver/ChangeLog:

	* Makefile.in (SFILES, OBS): Flatten list and order
	alphabetically.

gdb/testsuite/ChangeLog:

	* gdb.base/default.exp: Fix output of "set language".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Normalize names of some source files
@ 2016-11-23 16:36 sergiodj+buildbot
  2016-12-06 14:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23 16:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03b62bbbce3dc5f15131d9e78f77d035cd1cffb3 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 03b62bbbce3dc5f15131d9e78f77d035cd1cffb3

Normalize names of some source files

Most tdep/nat files are named:

  <cpu>-<os>-tdep.c
  <cpu>-<os>-nat.c

A few files do not respect this scheme.  This patch renames them so that
they are consistent with the rest of the files.  It builds fine with
--enable-targets=all, but that doesn't test the nat files.  I can only
hope that my grep skill is good enough.

gdb/ChangeLog:

	* Makefile.in (ALL_64_TARGET_OBS, ALL_TARGET_OBS,
	HFILES_NO_SRCDIR, ALLDEPFILES): Rename files.
	* alphabsd-nat.c: Rename to ...
	* alpha-bsd-nat.c: ... this, adjust include.
	* alphabsd-tdep.c: Rename to ...
	* alpha-bsd-tdep.c: ... this, adjust include.
	* alphabsd-tdep.h: Rename to ...
	* alpha-bsd-tdep.h: ... this, adjust include barrier and comment.
	* alphafbsd-tdep.c: Rename to ...
	* alpha-fbsd-tdep.c: ... this.
	* alphanbsd-tdep.c: Rename to ...
	* alpha-nbsd-tdep.c: ... this, adjust include.
	* alphaobsd-tdep.c: Rename to ...
	* alpha-obsd-tdep.c: ... this, adjust include.
	* amd64bsd-nat.c: Rename to ...
	* amd64-bsd-nat.c: ... this, adjust include.
	* amd64fbsd-nat.c: Rename to ...
	* amd64-fbsd-nat.c: ... this, adjust include.
	* amd64fbsd-tdep.c: Rename to ...
	* amd64-fbsd-tdep.c: ... this, adjust include.
	* amd64nbsd-nat.c: Rename to ...
	* amd64-nbsd-nat.c: ... this.
	* amd64nbsd-tdep.c: Rename to ...
	* amd64-nbsd-tdep.c: ... this.
	* amd64obsd-nat.c: Rename to ...
	* amd64-obsd-nat.c: ... this.
	* amd64obsd-tdep.c: Rename to ...
	* amd64-obsd-tdep.c: ... this.
	* amd64-tdep.h: Update comments.
	* armbsd-tdep.c: Rename to ...
	* arm-bsd-tdep.c: ... this.
	* armnbsd-nat.c: Rename to ...
	* arm-nbsd-nat.c: ... this.
	* armnbsd-tdep.c: Rename to ...
	* arm-nbsd-tdep.c: ... this.
	* armobsd-tdep.c: Rename to ...
	* arm-obsd-tdep.c: ... this.
	* arm-tdep.h: Update comments.
	* hppabsd-tdep.c: Rename to ...
	* hppa-bsd-tdep.c: ... this, adjust include.
	* hppabsd-tdep.h: Rename to ...
	* hppa-bsd-tdep.h: ... this, adjust include barrier and comment.
	* hppanbsd-nat.c: Rename to ...
	* hppa-nbsd-nat.c: ... this.
	* hppanbsd-tdep.c: Rename to ...
	* hppa-nbsd-tdep.c: ... this, adjust include.
	* hppaobsd-nat.c: Rename to ...
	* hppa-obsd-nat.c: ... this.
	* hppaobsd-tdep.c: Rename to ...
	* hppa-obsd-tdep.c: ... this, adjust include.
	* i386bsd-nat.c: Rename to ...
	* i386-bsd-nat.c: ... this, adjust include.
	* i386bsd-nat.h: Rename to ...
	* i386-bsd-nat.h: ... this, adjust include barrier and comment.
	* i386bsd-tdep.c: Rename to ...
	* i386-bsd-tdep.c: ... this.
	* i386fbsd-nat.c: Rename to ...
	* i386-fbsd-nat.c: ... this, adjust include.
	* i386fbsd-tdep.c: Rename to ...
	* i386-fbsd-tdep.c: ... this, adjust include.
	* i386fbsd-tdep.h: Rename to ...
	* i386-fbsd-tdep.h: ... this, adjust include barrier and comment.
	* i386gnu-nat.c: Rename to ...
	* i386-gnu-nat.c: ... this.
	* i386gnu-tdep.c: Rename to ...
	* i386-gnu-tdep.c: ... this.
	* i386nbsd-nat.c: Rename to ...
	* i386-nbsd-nat.c: ... this, adjust include.
	* i386nbsd-tdep.c: Rename to ...
	* i386-nbsd-tdep.c: ... this.
	* i386obsd-nat.c: Rename to ...
	* i386-obsd-nat.c: ... this, adjust include.
	* i386obsd-tdep.c: Rename to ...
	* i386-obsd-tdep.c: ... this.
	* i386v4-nat.c: Rename to ...
	* i386-v4-nat.c: ... this.
	* i386-tdep.h: Update comments.
	* m68k-tdep.h: Update comments.
	* m68kbsd-nat.c: Rename to ...
	* m68k-bsd-nat.c: ... this.
	* m68kbsd-tdep.c: Rename to ...
	* m68k-bsd-tdep.c: ... this.
	* m68klinux-nat.c: Rename to ...
	* m68k-linux-nat.c: ... this.
	* m68klinux-tdep.c: Rename to ...
	* m68k-linux-tdep.c: ... this.
	* m88kbsd-nat.c: Rename to ...
	* m88k-bsd-nat.c: ... this.
	* mipsnbsd-nat.c: Rename to ...
	* mips-nbsd-nat.c: ... this, adjust include.
	* mipsnbsd-tdep.c: Rename to ...
	* mips-nbsd-tdep.c: ... this, adjust include.
	* mipsnbsd-tdep.h: Rename to ...
	* mips-nbsd-tdep.h: ... this, adjust include barrier and comment.
	* mips64obsd-nat.c: Rename to ...
	* mips64-obsd-nat.c: ... this.
	* mips64obsd-tdep.c: Rename to ...
	* mips64-obsd-tdep.c: ... this.
	* ppcfbsd-nat.c: Rename to ...
	* ppc-fbsd-nat.c: ... this, adjust include.
	* ppcfbsd-tdep.c: Rename to ...
	* ppc-fbsd-tdep.c: ... this, adjust include.
	* ppcfbsd-tdep.h: Rename to ...
	* ppc-fbsd-tdep.h: ... this, adjust include barrier and comment.
	* ppcnbsd-nat.c: Rename to ...
	* ppc-nbsd-nat.c: ... this, adjust include.
	* ppcnbsd-tdep.c: Rename to ...
	* ppc-nbsd-tdep.c: ... this, adjust include.
	* ppcnbsd-tdep.h: Rename to ...
	* ppc-nbsd-tdep.h: ... this, adjust include barrier and comment.
	* ppcobsd-nat.c: Rename to ...
	* ppc-obsd-nat.c: ... this, adjust include.
	* ppcobsd-tdep.c: Rename to ...
	* ppc-obsd-tdep.c: ... this, adjust include.
	* ppcobsd-tdep.h: Rename to ...
	* ppc-obsd-tdep.h: ... this, adjust include barrier and comment.
	* shnbsd-nat.c: Rename to ...
	* sh-nbsd-nat.c: ... this.
	* shnbsd-tdep.c: Rename to ...
	* sh-nbsd-tdep.c: ... this.
	* sparcnbsd-nat.c: Rename to ...
	* sparc-nbsd-nat.c: ... this.
	* sparcnbsd-tdep.c: Rename to ...
	* sparc-nbsd-tdep.c: ... this.
	* sparcobsd-tdep.c: Rename to ...
	* sparc-obsd-tdep.c: ... this.
	* sparc64fbsd-nat.c: Rename to ...
	* sparc64-fbsd-nat.c: ... this.
	* sparc64fbsd-tdep.c: Rename to ...
	* sparc64-fbsd-tdep.c: ... this.
	* sparc64nbsd-nat.c: Rename to ...
	* sparc64-nbsd-nat.c: ... this.
	* sparc64nbsd-tdep.c: Rename to ...
	* sparc64-nbsd-tdep.c: ... this.
	* sparc64obsd-nat.c: Rename to ...
	* sparc64-obsd-nat.c: ... this.
	* sparc64obsd-tdep.c: Rename to ...
	* sparc64-obsd-tdep.c: ... this.
	* sparc64-tdep.h: Update comments.
	* vaxbsd-nat.c: Rename to ...
	* vax-bsd-nat.c: ... this.
	* vaxnbsd-tdep.c: Rename to ...
	* vax-nbsd-tdep.c: ... this.
	* vaxobsd-tdep.c: Rename to ...
	* vax-obsd-tdep.c: ... this.
	* x86bsd-nat.h: Rename to ...
	* x86-bsd-nat.h: ... this, adjust include barrier and comment.
	* x86bsd-nat.c: Rename to ...
	* x86-bsd-nat.c: ... this, adjust include.
	* configure.tgt: Update renamed files.
	* config/alpha/fbsd.mh: Update renamed files.
	* config/alpha/nbsd.mh: Update renamed files.
	* config/arm/nbsdelf.mh: Update renamed files.
	* config/djgpp/fnchange.lst: Update renamed files.
	* config/i386/fbsd.mh: Update renamed files.
	* config/i386/fbsd64.mh: Update renamed files.
	* config/i386/i386gnu.mh: Update renamed files.
	* config/i386/i386sol2.mh: Update renamed files.
	* config/i386/nbsd64.mh: Update renamed files.
	* config/i386/nbsdelf.mh: Update renamed files.
	* config/i386/obsd.mh: Update renamed files.
	* config/i386/obsd64.mh: Update renamed files.
	* config/i386/sol2-64.mh: Update renamed files.
	* config/m68k/linux.mh: Update renamed files.
	* config/m68k/nbsdelf.mh: Update renamed files.
	* config/m68k/obsd.mh: Update renamed files.
	* config/m88k/obsd.mh: Update renamed files.
	* config/mips/nbsd.mh: Update renamed files.
	* config/mips/obsd64.mh: Update renamed files.
	* config/pa/nbsd.mh: Update renamed files.
	* config/pa/obsd.mh: Update renamed files.
	* config/powerpc/fbsd.mh: Update renamed files.
	* config/powerpc/nbsd.mh: Update renamed files.
	* config/powerpc/obsd.mh: Update renamed files.
	* config/sh/nbsd.mh: Update renamed files.
	* config/sparc/fbsd.mh: Update renamed files.
	* config/sparc/nbsd64.mh: Update renamed files.
	* config/sparc/nbsdelf.mh: Update renamed files.
	* config/sparc/obsd64.mh: Update renamed files.
	* config/vax/nbsdelf.mh: Update renamed files.
	* config/vax/obsd.mh: Update renamed files.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Minor formatting fixups in Makefiles
@ 2016-11-23 17:10 sergiodj+buildbot
  2016-12-06 15:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23 17:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8629c02c0db6ff3f7444397567a57dd36a3eed41 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 8629c02c0db6ff3f7444397567a57dd36a3eed41

Minor formatting fixups in Makefiles

Mostly some whitespace changes to make things a bit more consistent.

gdb/ChangeLog:

	* Makefile.in: Fix whitespace formatting.

gdb/gdbserver/ChangeLog:

	* Makefile.in: Fix whitespace formatting.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Use C++11 std::chrono
@ 2016-11-23 17:24 sergiodj+buildbot
  2016-12-06 18:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-23 17:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dcb07cfa156a8e9f768c7f2b5d32f27b6dfe939f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: dcb07cfa156a8e9f768c7f2b5d32f27b6dfe939f

gdb: Use C++11 std::chrono

This patch fixes a few problems with GDB's time handling.

#1 - It avoids problems with gnulib's C++ namespace support

On MinGW, the struct timeval that should be passed to gnulib's
gettimeofday replacement is incompatible with libiberty's
timeval_sub/timeval_add.  That's because gnulib also replaces "struct
timeval" with its own definition, while libiberty expects the
system's.

E.g., in code like this:

  gettimeofday (&prompt_ended, NULL);
  timeval_sub (&prompt_delta, &prompt_ended, &prompt_started);
  timeval_add (&prompt_for_continue_wait_time,
               &prompt_for_continue_wait_time, &prompt_delta);

That's currently handled in gdb by not using gnulib's gettimeofday at
all (see common/gdb_sys_time.h), but that #undef hack won't work with
if/when we enable gnulib's C++ namespace support, because that mode
adds compile time warnings for uses of ::gettimeofday, which are hard
errors with -Werror.

#2 - But there's an elephant in the room: gettimeofday is not monotonic...

We're using it to:

  a) check how long functions take, for performance analysis
  b) compute when in the future to fire events in the event-loop
  c) print debug timestamps

But that's exactly what gettimeofday is NOT meant for.  Straight from
the man page:

~~~
       The time returned by gettimeofday() is affected by
       discontinuous jumps in the system time (e.g., if the system
       administrator manually changes the system time).  If you need a
       monotonically increasing clock, see clock_gettime(2).
~~~

std::chrono (part of the C++11 standard library) has a monotonic clock
exactly for such purposes (std::chrono::steady_clock).  This commit
switches to use that instead of gettimeofday, fixing all the issues
mentioned above.

gdb/ChangeLog:
2016-11-23  Pedro Alves  <palves@redhat.com>

	* Makefile.in (SFILES): Add common/run-time-clock.c.
	(HFILES_NO_SRCDIR): Add common/run-time-clock.h.
	(COMMON_OBS): Add run-time-clock.o.
	* common/run-time-clock.c, common/run-time-clock.h: New files.
	* defs.h (struct timeval, print_transfer_performance): Delete
	declarations.
	* event-loop.c (struct gdb_timer) <when>: Now a
	std::chrono::steady_clock::time_point.
	(create_timer): use std::chrono::steady_clock instead of
	gettimeofday.  Use new instead of malloc.
	(delete_timer): Use delete instead of xfree.
	(duration_cast_timeval): New.
	(update_wait_timeout): Use std::chrono::steady_clock instead of
	gettimeofday.
	* maint.c: Include <chrono> instead of "gdb_sys_time.h", <time.h>
	and "timeval-utils.h".
	(scoped_command_stats::~scoped_command_stats)
	(scoped_command_stats::scoped_command_stats): Use
	std::chrono::steady_clock instead of gettimeofday.  Use
	user_cpu_time_clock instead of get_run_time.
	* maint.h: Include "run-time-clock.h" and <chrono>.
	(scoped_command_stats): <m_start_cpu_time>: Now a
	user_cpu_time_clock::time_point.
	<m_start_wall_time>: Now a std::chrono::steady_clock::time_point.
	* mi/mi-main.c: Include "run-time-clock.h" and <chrono> instead of
	"gdb_sys_time.h" and <sys/resource.h>.
	(rusage): Delete.
	(mi_execute_command): Use new instead of XNEW.
	(mi_load_progress): Use std::chrono::steady_clock instead of
	gettimeofday.
	(timestamp): Rewrite in terms of std::chrono::steady_clock,
	user_cpu_time_clock and system_cpu_time_clock.
	(timeval_diff): Delete.
	(print_diff): Adjust to use std::chrono::steady_clock,
	user_cpu_time_clock and system_cpu_time_clock.
	* mi/mi-parse.h: Include "run-time-clock.h" and <chrono> instead
	of "gdb_sys_time.h".
	(struct mi_timestamp): Change fields types to
	std::chrono::steady_clock::time_point, user_cpu_time_clock::time
	and system_cpu_time_clock::time_point, instead of struct timeval.
	* symfile.c: Include <chrono> instead of <time.h> and
	"gdb_sys_time.h".
	(struct time_range): New.
	(generic_load): Use std::chrono::steady_clock instead of
	gettimeofday.
	(print_transfer_performance): Replace timeval parameters with a
	std::chrono::steady_clock::duration parameter.  Adjust.
	* utils.c: Include <chrono> instead of "timeval-utils.h",
	"gdb_sys_time.h", and <time.h>.
	(prompt_for_continue_wait_time): Now a
	std::chrono::steady_clock::duration.
	(defaulted_query, prompt_for_continue): Use
	std::chrono::steady_clock instead of
	gettimeofday/timeval_sub/timeval_add.
	(reset_prompt_for_continue_wait_time): Use
	std::chrono::steady_clock::duration instead of struct timeval.
	(get_prompt_for_continue_wait_time): Return a
	std::chrono::steady_clock::duration instead of struct timeval.
	(vfprintf_unfiltered): Use std::chrono::steady_clock instead of
	gettimeofday.  Use std::string.  Use '.' instead of ':'.
	* utils.h: Include <chrono>.
	(get_prompt_for_continue_wait_time): Return a
	std::chrono::steady_clock::duration instead of struct timeval.

gdb/gdbserver/ChangeLog:
2016-11-23  Pedro Alves  <palves@redhat.com>

	* debug.c: Include <chrono> instead of "gdb_sys_time.h".
	(debug_vprintf): Use std::chrono::steady_clock instead of
	gettimeofday.  Use '.' instead of ':'.
	* tracepoint.c: Include <chrono> instead of "gdb_sys_time.h".
	(get_timestamp): Use std::chrono::steady_clock instead of
	gettimeofday.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] RISC-V/bfd: Fix bitsize of R_RISCV_ADD8.
@ 2016-11-24  3:59 sergiodj+buildbot
  2016-12-06 21:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-24  3:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b14696aedc2b56291bc98d62fe232c8dceb1385 ***

Author: Kuan-Lin Chen <kuanlinchentw@gmail.com>
Branch: master
Commit: 0b14696aedc2b56291bc98d62fe232c8dceb1385

RISC-V/bfd: Fix bitsize of R_RISCV_ADD8.

bfd/ChangeLog:
	* bfd/elfxx-riscv.c (howto_table): Fix bitsize of R_RISCV_ADD8.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] Bind defined symbol locally in PIE
@ 2016-11-24 14:48 sergiodj+buildbot
  2016-12-07  3:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 14:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1dcb9720d62cd053a72c31881b7724ce9f74332c ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 1dcb9720d62cd053a72c31881b7724ce9f74332c

[ARM] Bind defined symbol locally in PIE

bfd/
	PR target/20737
	* elf32-arm.c (elf32_arm_final_link_relocate): Bind defined symbol
	locally in PIE.

ld/
	* testsuite/ld-arm/pie-bind-locally-a.s: New test source.
	* testsuite/ld-arm/pie-bind-locally-b.s: Likewise.
	* testsuite/ld-arm/pie-bind-locally.d: New testcase.
	* testsuite/ld-arm/arm-elf.exp: Run new testcase.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR12616 - gdb does not implement DW_AT_data_bit_offset
@ 2016-11-24 17:53 sergiodj+buildbot
  2016-12-07  5:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 17:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da5b30da2d1167591aa8d71b543f97bfdc2ec2a2 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: da5b30da2d1167591aa8d71b543f97bfdc2ec2a2

Fix PR12616 - gdb does not implement DW_AT_data_bit_offset

The DW_AT_data_bit_offset attribute was introduced by DWARF V4 and
allows specifying the offset of a data member within its containing
entity.  But although the new attribute was intended to replace
DW_AT_bit_offset for this purpose, GDB ignores it, and thus GCC still
emits DW_AT_bit_offset instead.  See also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71669.

This change fixes GDB's lack of support for DW_AT_data_bit_offset and
adds an appropriate test case.

gdb/ChangeLog:

	PR gdb/12616
	* dwarf2read.c (dwarf2_add_field): Handle the DWARF V4 attribute
	DW_AT_data_bit_offset.

gdb/testsuite/ChangeLog:

	PR gdb/12616
	* gdb.dwarf2/nonvar-access.exp: New testcase.  Check that GDB
	respects the DW_AT_data_bit_offset attribute.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix copy_bitwise()
@ 2016-11-24 18:47 sergiodj+buildbot
  2016-12-07  9:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22347e554cd7ba2a0bf36dc81ebfcbe2e2fd74af ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 22347e554cd7ba2a0bf36dc81ebfcbe2e2fd74af

Fix copy_bitwise()

When the user writes or reads a variable whose location is described
with DWARF pieces (DW_OP_piece or DW_OP_bit_piece), GDB's helper
function copy_bitwise is invoked for each piece.  The implementation of
this function has a bug that may result in a corrupted copy, depending
on alignment and bit size.  (Full-byte copies are not affected.)

This rewrites copy_bitwise, replacing its algorithm by a fixed version,
and adding an appropriate test case.  Without the fix the new test case
fails, e.g.:

  print def_t
  $2 = {a = 0, b = 4177919}
  (gdb) FAIL: gdb.dwarf2/nonvar-access.exp: print def_t

Written in binary, the wrong result above looks like this:

  01111111011111111111111

Which means that two zero bits have sneaked into the copy of the
original all-one bit pattern.  The test uses this simple all-one value
in order to avoid another GDB bug that causes the DWARF piece of a
DW_OP_stack_value to be taken from the wrong end on big-endian
architectures.

gdb/ChangeLog:

	* dwarf2loc.c (extract_bits_primitive): Remove.
	(extract_bits): Remove.
	(copy_bitwise): Rewrite.  Fixes a possible corruption that may
	occur for non-byte-aligned copies.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/nonvar-access.exp: Add a test for accessing
	non-byte-aligned bit fields.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add unit test for copy_bitwise
@ 2016-11-24 19:13 sergiodj+buildbot
  2016-12-07 10:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad06383f106ccfa299a6c7ac9720178d2d3d583f ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: ad06383f106ccfa299a6c7ac9720178d2d3d583f

Add unit test for copy_bitwise

This adds a unit test for the copy_bitwise function in dwarf2loc.c.
With the old (broken) version of copy_bitwise this test would generate
the following failure message:

(gdb) maintenance selftest
Self test failed: copy_bitwise 11000000 != 10000000 (7+2 -> 0)

gdb/ChangeLog:
2016-11-24  Andreas Arnez  <arnez@linux.vnet.ibm.com>
	    Pedro Alves  <palves@redhat.com>

	* dwarf2loc.c (bits_to_str, check_copy_bitwise)
	(copy_bitwise_tests): New functions.
	(_initialize_dwarf2loc): Register the new function
	copy_bitwise_tests as a unit test.
	* selftest.c (run_self_tests): Improve the failure message's
	wording and formatting.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Optimize byte-aligned copies in copy_bitwise()
@ 2016-11-24 19:17 sergiodj+buildbot
  2016-12-07 12:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 19:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 793c128d03113816db85e8d1fa0bcd4982e246ee ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 793c128d03113816db85e8d1fa0bcd4982e246ee

Optimize byte-aligned copies in copy_bitwise()

The function copy_bitwise used for copying DWARF pieces can potentially
be invoked for large chunks of data.  For instance, consider a large
struct one of whose members is currently located in a register.  In this
case copy_bitwise would still copy the data bitwise in a loop, which is
much slower than necessary.

This change uses memcpy for the large part instead, if possible.

gdb/ChangeLog:

	* dwarf2loc.c (copy_bitwise): Use memcpy for the middle part, if
	it is byte-aligned.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add noexcept to custom non-throwing new operators.
@ 2016-11-24 21:00 sergiodj+buildbot
  2016-12-07 15:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bbe910e6e1140cb484a74911f3cea854cf9e7e2a ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: bbe910e6e1140cb484a74911f3cea854cf9e7e2a

Add noexcept to custom non-throwing new operators.

Both libc++ and libstdc++ declare non-throwing new operators as
noexcept and overloads must also be noexcept.  This fixes a
-Wmissing-exception-spec warning with clang.

gdb/ChangeLog:

	* common/new-op.c (operator new): Mark 'noexcept'.
	(operator new[]): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Do not use std::move when assigning an anonymous object to a unique_ptr.
@ 2016-11-24 21:27 sergiodj+buildbot
  2016-12-07 19:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 21:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 036e657b48144d7449ddfcfcf9214bcd7bcf268b ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 036e657b48144d7449ddfcfcf9214bcd7bcf268b

Do not use std::move when assigning an anonymous object to a unique_ptr.

Using std::move forces an extra copy of the object.  These changes fix
-Wpessimizing-move warnings from clang.

gdb/ChangeLog:

	* ada-lang.c (create_excep_cond_exprs): Do not use 'std::move'.
	* ax-gdb.c (agent_eval_command_one): Likewise.
	(agent_eval_command_one): Likewise.
	* breakpoint.c (parse_cond_to_aexpr): Likewise.
	(parse_cmd_to_aexpr): Likewise.
	* dtrace-probe.c (dtrace_process_dof_probe): Likewise.
	* parse.c (parse_expression_for_completion): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Prevent problems with section alignment by not shrinking the .rsrc section.
@ 2016-11-25 10:36 sergiodj+buildbot
  2016-12-07 22:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-25 10:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec8f76882145c71bef81a9cadf0bf51ff9fa5b35 ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: ec8f76882145c71bef81a9cadf0bf51ff9fa5b35

Prevent problems with section alignment by not shrinking the .rsrc section.

	PR ld/20193
	* peXXigen.c (rsrc_process_section): Do not shrink the merged
	.rsrc section.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix typos in comment
@ 2016-11-25 15:36 sergiodj+buildbot
  2016-12-08  4:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-25 15:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ce9efb079b6e7b3ab2e795db9477656375d7204 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8ce9efb079b6e7b3ab2e795db9477656375d7204

Fix typos in comment

gdb/ChangeLog:

	* record-full.c (record_full_resume): Fix typos in comment.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix typo in comment
@ 2016-11-25 16:29 sergiodj+buildbot
  2016-12-08  2:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-25 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17e5269b995b0560dc74af78ba134cf1fcd9d56a ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 17e5269b995b0560dc74af78ba134cf1fcd9d56a

Fix typo in comment

gdb/ChangeLog:

	* infcmd.c (interrupt_command): Fix typo in comment.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix typo in Makefile
@ 2016-11-25 17:47 sergiodj+buildbot
  2016-12-08  7:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-25 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50cc587fe49621a87283f06655fe922d45095076 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 50cc587fe49621a87283f06655fe922d45095076

Fix typo in Makefile

Fix a typo I made in my previous Makefile cleanup series.

Thanks to Patrick Monnerat for reporting.

gdb/ChangeLog:

	* Makefile.in: Fix typo.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove check requiring void argument to functions with no parameters.
@ 2016-11-25 21:27 sergiodj+buildbot
  2016-12-08 10:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-25 21:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8227ffad95fcd835dd5fcb3e4915159e4552b397 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 8227ffad95fcd835dd5fcb3e4915159e4552b397

Remove check requiring void argument to functions with no parameters.

C++ treats an empty parameter list as no parameters unlike C.

gdb/ChangeLog:

	* contrib/ari/gdb_ari.sh (no parameter function): Remove check.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove stale comments
@ 2016-11-26 15:59 sergiodj+buildbot
  2016-12-08 12:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-26 15:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 59b21252a88aa6ba488cfb19686d9cbad2577e76 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 59b21252a88aa6ba488cfb19686d9cbad2577e76

Remove stale comments

The default ui_out is gone since commit
23ff98d2fed4a1eaeb815e18cd4169e5aa7aaa60.

gdb/ChangeLog:

	* ui-out.h (struct ui_out_impl): Remove comment.
	* ui-out.c (struct ui_out): Remove comment.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove unused functions and declarations
@ 2016-11-27  4:20 sergiodj+buildbot
  2016-12-08 15:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-27  4:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f904c28f5cd2dc91a118ae6169d6993aaf71f63 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 7f904c28f5cd2dc91a118ae6169d6993aaf71f63

Remove unused functions and declarations

gdb/ChangeLog:

	* ui-out.c (_initialize_ui_out): Remove.
	(ui_out_set_flags): Remove.
	(ui_out_clear_flags): Remove.
	* ui-out.h (ui_out_begin_cleanup_end): Remove.
	(ui_out_begin_cleanup_end): Remove.
	(ui_out_set_flags): Remove.
	(ui_out_clear_flags): Remove.
	* mi/mi-out.c (_initialize_mi_out): Remove.
	(mi_out_buffered): Remove.
	* mi/mi-out.h (mi_out_buffered): Remove.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Rename ui_out_data to mi_ui_out_data
@ 2016-11-27  4:37 sergiodj+buildbot
  2016-12-08 19:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-27  4:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0abe66b59fda0689c32fe9d96b3690b4d49a3027 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 0abe66b59fda0689c32fe9d96b3690b4d49a3027

Rename ui_out_data to mi_ui_out_data

Just a little cleanup, so the name is more consistent with the naming of
the equivalent structures of cli and tui.  It goes away in subsequent
patches anyway, but it might help follow the changes in those patches...

gdb/ChangeLog:

	* mi/mi-out.c (ui_out_data): Rename to ...
	(mi_ui_out_data): ... this.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove ui_out_destroy
@ 2016-11-27  5:37 sergiodj+buildbot
  2016-12-08 22:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-27  5:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e4975d6a9cd8aaf3fb14135b36850964def131d7 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: e4975d6a9cd8aaf3fb14135b36850964def131d7

Remove ui_out_destroy

It's not actually used, and removing it simplifies the upcoming patches
a bit.  After the whole series, destroying an ui_out object will be
simply "delete uiout", which will call the default destructor.

gdb/ChangeLog:

	* ui-out.c (ui_out_destroy, uo_data_destroy): Remove.
	* ui-out.h (ui_out_destroy): Remove.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix return value of uo_redirect
@ 2016-11-27  5:56 sergiodj+buildbot
  2016-12-09  0:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-27  5:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82bbe65a43015a753bec8c64869679a699331a5b ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 82bbe65a43015a753bec8c64869679a699331a5b

Fix return value of uo_redirect

The wrapper uo_redirect seems like it should return the return value
from of implementation function, since callers rely on it, but it
doesn't.

gdb/ChangeLog:

	* ui-out.c (uo_redirect): Return the return value from the
	implementation function.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Constify wrap_here/wrap_hint code path
@ 2016-11-27  8:16 sergiodj+buildbot
  2016-12-09  4:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-27  8:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2c0eef48a1bb331ca08f8f26ff82c5d4086ba0c ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: d2c0eef48a1bb331ca08f8f26ff82c5d4086ba0c

Constify wrap_here/wrap_hint code path

Constify the data path between ui_out_wrap_hint and the wrap_indent
global, because we can.  It's clearer that the argument passed to
wrap_hint is not intended to be modified by the ui_out implementation.

gdb/ChangeLog:

	* mi/mi-out.c (mi_wrap_hint): Constify argument.
	* cli-out.c (cli_wrap_hint): Likewise.
	* ui-out.c (ui_out_wrap_hint, uo_wrap_hint): Likewise.
	* ui-out.h (ui_out_wrap_hint, wrap_hint_ftype): Likewise.
	* utils.c (wrap_here): Likewise.
	(wrap_indent): Constify.
	* utils.h (wrap_here): Constify argument.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove verbosity from ui_out_message and friends
@ 2016-11-27  8:30 sergiodj+buildbot
  2016-12-09  6:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-27  8:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7fb048a2ee38bbc85ba0e96e2932cb0cb1f7381e ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 7fb048a2ee38bbc85ba0e96e2932cb0cb1f7381e

Remove verbosity from ui_out_message and friends

That concept is never actually used, so it's just a burden.  Removing it
facilitates the refactoring in upcoming patches.

gdb/ChangeLog:

	* mi/mi-out.c (mi_message): Remove verbosity argument.
	* ada-tasks.c (print_ada_task_info, info_task, task_command):
	Update call.
	* auto-load.c (auto_load_info_scripts): Likewise.
	* breakpoint.c (breakpoint_1, watchpoints_info, tracepoints_info):
	Likewise.
	* cli-out.c (cli_message): Remove verbosity argument.
	* inferior.c (print_inferior): Update call.
	* linux-thread-db.c (info_auto_load_libthread_db): Likewise.
	* probe.c (info_probes_for_ops): Likewise.
	* skip.c (skip_info): Likewise.
	* solib.c (info_sharedlibrary_command): Likewise.
	* symfile.c (load_progress): Likewise.
	* thread.c (print_thread_info_1): Likewise.
	* ui-out.c (uo_message, ui_out_message): Remove verbosity argument.
	(ui_out_get_verblvl): Remove.
	* ui-out.h (ui_out_message): Remove verbosity argument.
	(ui_out_get_verblvl): Remove.
	(message_ftype): Remove verbosity argument.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Properly hide hidden versioned symbol in executable
@ 2016-11-28 16:35 sergiodj+buildbot
  2016-12-09 17:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-28 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4deb8f714d555a2f530e37c3e7af32bc42fdda58 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 4deb8f714d555a2f530e37c3e7af32bc42fdda58

Properly hide hidden versioned symbol in executable

A hidden versioned symbol in executable should be forced local if it is
locally defined, not referenced by shared library and not exported.  We
must do it before _bfd_elf_link_renumber_dynsyms.

bfd/

	* elflink.c (_bfd_elf_fix_symbol_flags): Hide hidden versioned
	symbol in executable.
	(elf_link_output_extsym): Don't change bind from global to
	local when linking executable.

ld/

	* testsuite/ld-elf/indirect.exp: Add a test for PR 18720.
	* testsuite/ld-elf/pr18720.rd: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Move computed value's frame id to piece_closure
@ 2016-11-28 17:50 sergiodj+buildbot
  2016-12-09 20:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-28 17:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee40d8d45213caf0cfb63e603f0fd5a58532e751 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ee40d8d45213caf0cfb63e603f0fd5a58532e751

Move computed value's frame id to piece_closure

Nowadays, we set computed value's frame id, which is a misuse to me.
The computed value itself doesn't care about frame id, but function
value_computed_funcs (val)->read (or read_pieced_value) cares about
which frame the register is relative to, so 'struct piece_closure' is
a better place to fit frame id.

This patch adds a frame id in 'struct piece_closure', and use it
instead of using computed value's frame id.

gdb:

2016-11-28  Yao Qi  <yao.qi@linaro.org>

	* dwarf2loc.c (struct piece_closure) <frame_id>: New field.
	(allocate_piece_closure): Add new parameter 'frame' and set
	closure's frame_id field accordingly.
	(read_pieced_value): Get frame from closure instead of value.
	(dwarf2_evaluate_loc_desc_full): Remove code getting frame id.
	Don't set value's frame id.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Adjust Value.location for lval_register
@ 2016-11-28 19:26 sergiodj+buildbot
  2016-12-09 23:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-28 19:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7dc54575d91a2b41f6c3e838eec44a7017a24436 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7dc54575d91a2b41f6c3e838eec44a7017a24436

Adjust Value.location for lval_register

value.regnum and value.next_frame_id are only used for lval_register,
so this patch moves them to union value.location.  As a result, when
we copy value, only copy location, don't need to copy regnum and
next_frame_id.

This patch also changes regnum's type to int as there is no space
constraint, so update deprecated_value_regnum_hack return type too.

gdb:

2016-11-28  Yao Qi  <yao.qi@linaro.org>

	* valops.c (value_slice): Don't set frame id of slice.
	* value.c (struct value) <regnum, next_frame_id>: Move them to...
	(struct value) <location>: ... here.  Update comments.
	(allocate_value_lazy): Don't set frame id and regnum.
	(deprecated_value_next_frame_id_hack): Adjust.
	(deprecated_value_regnum_hack): Adjust.
	(value_copy): Don't copy frame id and regnu.
	(value_primitive_field): Likewise.
	(value_from_component): Likewise.
	(deprecated_value_regnum_hack): Return int *.
	* value.h (deprecated_value_regnum_hack): Update declaration.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Restrict checking value.lval on using address
@ 2016-11-28 19:38 sergiodj+buildbot
  2016-12-10  3:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-28 19:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a0884415891b197972f8acf59131c3c9376807f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1a0884415891b197972f8acf59131c3c9376807f

Restrict checking value.lval on using address

With the previous change, value.location.address is only valid for
lval_memory.  This patch restrict some checking on value.lval on
using address.  Since we have a check on VALUE_VAL in
set_value_address, we need to set VALUE_VAL properly before
set_value_address too.

gdb:

2016-11-25  Yao Qi  <yao.qi@linaro.org>

	* ada-lang.c (ensure_lval): Call set_value_address after setting
	VALUE_LVAL.
	* elfread.c (elf_gnu_ifunc_resolve_addr): Set VALUE_LVAL to
	lval_memory.
	(elf_gnu_ifunc_resolver_return_stop): Likewise.
	* value.c (value_fn_field): Likewise.
	(value_from_contents_and_address_unresolved): Likewise.
	(value_from_contents_and_address): Likewise.
	(value_address): Check value->lval isn't
	lval_memory.
	(value_raw_address): Likewise.
	(set_value_address): Assert value->lval is lval_memory.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Partially revert patch for PR 20815 - do not sort the PT_LOAD segments. Non-ordered segments are needed by the Linux kernel.
@ 2016-11-28 20:51 sergiodj+buildbot
  2016-12-10  8:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-28 20:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd58485720b47d80fed0b281d15a9198f43eaf0c ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: cd58485720b47d80fed0b281d15a9198f43eaf0c

Partially revert patch for PR 20815 - do not sort the PT_LOAD segments.  Non-ordered segments are needed by the Linux kernel.

	PR ld/20815
	* elf.c (phdr_sorter): Delete.
	(assign_file_positions_except_relocs): Do not sort program
	headers.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] X86: Ignore REX_B bit for 32-bit XOP instructions
@ 2016-11-28 21:09 sergiodj+buildbot
  2016-12-10  5:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-28 21:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT abfcb414b9900ef996b1665323a950610dbdca43 ***

Author: Amit Pawar <Amit.Pawar@amd.com>
Branch: master
Commit: abfcb414b9900ef996b1665323a950610dbdca43

X86: Ignore REX_B bit for 32-bit XOP instructions

While decoding 32-bit XOP instructions, 64 bit registers names are printed.
This patch fixes this by ignoring REX_B bit in 32-bit mode.

opcodes/

	PR binutils/20637
	* i386-dis.c (get_valid_dis386): Ignore REX_B for 32-bit XOP
	instructions.

gas/

	PR binutils/20637
	* testsuite/gas/i386/xop32reg.d: New file.
	* testsuite/gas/i386/xop32reg.s: New file.
	* testsuite/gas/i386/i386.exp: Run new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix debug output in record_full_open_1
@ 2016-11-29  3:18 sergiodj+buildbot
  2016-12-10 12:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-29  3:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a0640e3ba9a668c4c317520c48246e1cc8d75ca ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 0a0640e3ba9a668c4c317520c48246e1cc8d75ca

Fix debug output in record_full_open_1

The printed function name should be record_full_open_1, not
record_full_open.

gdb/ChangeLog:

	* record-full.c (record_full_open_1): Fix debug output.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARC] Fix disassembler option.
@ 2016-11-29 11:20 sergiodj+buildbot
  2016-12-10 15:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-29 11:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee881e5d3312ea5396bddc37e8673b77bf549b4b ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: ee881e5d3312ea5396bddc37e8673b77bf549b4b

[ARC] Fix disassembler option.

This patch fixes:
- fpus and fpud are swaped.
- quarkse_em doesn't include FPX extensions.
- auto guessed opcode mechanism may ignore the option passed via -M<feature> option.

opcodes/
2016-11-29  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-dis.c (is_compatible_p): Remove function.
	(skip_this_opcode): Don't add any decoding class to decode list.
	Remove warning.
	(find_format_from_table): Go through all opcodes, and warn if we
	use a guessed mnemonic.

binutils/
2016-11-29  Claudiu Zissulescu  <claziss@synopsys.com>

	* testsuite/binutils-all/arc/objdump.exp (Warning test): Update
	test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARC] Add checking for LP_COUNT reg usage, improve error reporting.
@ 2016-11-29 12:01 sergiodj+buildbot
  2016-12-10 17:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-29 12:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT abe7c33b45288b407e6d001aad713183d4bab5c6 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: abe7c33b45288b407e6d001aad713183d4bab5c6

[ARC] Add checking for LP_COUNT reg usage, improve error reporting.

gas/
2016-11-29  Claudiu Zissulescu  <claziss@synopsys.com>

	* config/tc-arc.c (find_opcode_match): New function argument
	errmsg.
	(assemble_tokens): Collect and report the eventual error message
	found during opcode matching process.
	* testsuite/gas/arc/lpcount-err.s: New file.
	* testsuite/gas/arc/add_s-err.s: Update error message.

opcode/
2016-11-29  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-opc.c (insert_ra_chk): New function.
	(insert_rb_chk): Likewise.
	(insert_rad): Update text error message.
	(insert_rcd): Likewise.
	(insert_rhv2): Likewise.
	(insert_r0): Likewise.
	(insert_r1): Likewise.
	(insert_r2): Likewise.
	(insert_r3): Likewise.
	(insert_sp): Likewise.
	(insert_gp): Likewise.
	(insert_pcl): Likewise.
	(insert_blink): Likewise.
	(insert_ilink1): Likewise.
	(insert_ilink2): Likewise.
	(insert_ras): Likewise.
	(insert_rbs): Likewise.
	(insert_rcs): Likewise.
	(insert_simm3s): Likewise.
	(insert_rrange): Likewise.
	(insert_fpel): Likewise.
	(insert_blinkel): Likewise.
	(insert_pcel): Likewise.
	(insert_nps_3bit_dst): Likewise.
	(insert_nps_3bit_dst_short): Likewise.
	(insert_nps_3bit_src2_short): Likewise.
	(insert_nps_bitop_size_2b): Likewise.
	(MAKE_SRC_POS_INSERT_EXTRACT_FUNCS): Likewise.
	(RA_CHK): Define.
	(RB): Adjust.
	(RB_CHK): Define.
	(RC): Adjust.
	* arc-dis.c (print_insn_arc): Add LOAD and STORE class.
	* arc-tbl.h (div, divu): All instructions are DIVREM class.
	Change first insn argument to check for LP_COUNT usage.
	(rem): Likewise.
	(ld, ldd): All instructions are LOAD class.  Change first insn
	argument to check for LP_COUNT usage.
	(st, std): All instructions are STORE class.
	(mac, mpy, dmac, mul, dmpy): All instructions are MPY class.
	Change first insn argument to check for LP_COUNT usage.
	(mov): All instructions are MOVE class.  Change first insn
	argument to check for LP_COUNT usage.

include/
2016-11-29  Claudiu Zissulescu  <claziss@synopsys.com>

	* opcode/arc.h (insn_class_t): Add DIVREM, LOAD, MOVE, MPY, STORE
	instruction classes.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR20886, looping in ppc64_elf_size_stubs
@ 2016-11-30  7:01 sergiodj+buildbot
  2016-12-10 20:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-30  7:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea3d7d1cab4221ab729327bb4d957352c79d05f0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: ea3d7d1cab4221ab729327bb4d957352c79d05f0

PR20886, looping in ppc64_elf_size_stubs

The PR20886 binary is large enough that there are two stub sections
servicing .text (which is 88M).  It so happens that between one
iteration of sizing and the next that one stub section grows while
the other shrinks.  Since one section is always growing, the loop
never terminates.

This patch changes the algorithm to not update previous size on
shrinking, once we go past a certain number of iterations.

	PR ld/20886
	* elf64-ppc.c (ppc64_elf_size_stubs): Make rawsize max size seen
	on any pass past STUB_SHRINK_ITER.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Revert accidental elf.c change
@ 2016-11-30 12:13 sergiodj+buildbot
  2016-12-11  3:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-30 12:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9a38e0f5287ce7b4629f5f923191e38dd7355c0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: e9a38e0f5287ce7b4629f5f923191e38dd7355c0

Revert accidental elf.c change

	* elf.c (get_program_header_size): Revert accidental change.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARM] Read memory as unsigned integer
@ 2016-11-30 12:39 sergiodj+buildbot
  2016-12-11  5:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-30 12:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7913a64cab3930fe524f0e38f85cfca11bd52dcb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7913a64cab3930fe524f0e38f85cfca11bd52dcb

[ARM] Read memory as unsigned integer

When GDB read inferior memory as an address or an instruction,
it should be unsigned.

gdb:

2016-11-30  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (arm_scan_prologue): Read memory as unsigned integer.
	(arm_exidx_unwind_sniffer): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Makefiles: Disable suffix rules and implicit rules
@ 2016-11-30 21:56 sergiodj+buildbot
  2016-12-11  8:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-11-30 21:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad02e4fe877f3a874145dd045626501245e65624 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: ad02e4fe877f3a874145dd045626501245e65624

Makefiles: Disable suffix rules and implicit rules

Since we don't use suffix rules nor implicit rules in gdb, we can
disable them.  The advantage is a slightly faster make [1].

Here are some numbers about the speedup.  I ran this on my trusty old
Intel Q6600, so the time numbers are probably higher than what you'd get
on any recent hardware.  I ran "make" in the gdb/ directory of an
already built repository (configured with --enable-targets=all).  I
recorded the time of execution (average of 5).  I then ran "make -d" and
recorded the number of printed lines, which gives a rough idea of the
number of operations done.

I compared the following configurations, to see the impact of both the
empty .SUFFIXES target and the empty pattern rules, as well as running
"make -r", which can be considered the "ideal" case.

 A - baseline
 B - baseline + .SUFFIXES
 C - baseline + pattern rules
 D - baseline + .SUFFIXES + pattern rules
 E - baseline + make -r

 config | time (s) | "make -d"
 -----------------------------
    A   |   5.74   |  2396643
    B   |   1.19   |   298469
    C   |   2.81   |  1266573
    D   |   1.13   |   245489
    E   |   1.01   |   163914

We can see that the empty .SUFFIXES target has a bigger impact than the
empty pattern rules, but still it doesn't hurt to disable the implicit
pattern rules as well.

There are still some mentions of implicit rules I can't get rid of in
the "make -d" output.  For example, it's trying to build .c files from
.w files:

  Looking for an implicit rule for '/home/simark/src/binutils-gdb/gdb/infrun.c'.
  Trying pattern rule with stem 'infrun'.
  Trying implicit prerequisite '/home/simark/src/binutils-gdb/gdb/infrun.w'.

and trying to build Makefile.in from a bunch of extensions:

  Looking for an implicit rule for 'Makefile.in'.
  Trying pattern rule with stem 'Makefile.in'.
  Trying implicit prerequisite 'Makefile.in.o'.
  Trying pattern rule with stem 'Makefile.in'.
  Trying implicit prerequisite 'Makefile.in.c'.
  Trying pattern rule with stem 'Makefile.in'.
  Trying implicit prerequisite 'Makefile.in.cc'.
  ... many more ...

If somebody knows how to disable them, we can do it, but at this point
the returns are minimal, so it is not that important.

I verified that both in-tree and out-of-tree builds work.

[1] Switching from explicit rules to pattern rules for files in
    subdirectories actually made it slower, so this is kind of a way to
    redeem myself.  But it the end it's faster than it was previously,
    so it was all worth it. :)

gdb/ChangeLog:

	* disable-implicit-rules.mk: New file.
	* Makefile.in: Include disable-implicit-rules.mk.
	* data-directory/Makefile.in: Likewise.
	* gnulib/Makefile.in: Likewise.

gdb/doc/ChangeLog:

	* Makefile.in: Likewise.

gdb/gdbserver/ChangeLog:

	* Makefile.in: Include disable-implicit-rules.mk.

gdb/testsuite/ChangeLog:

	* Makefile.in: Include disable-implicit-rules.mk.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use new/delete instead of malloc/free-based functions
@ 2016-12-01  3:08 sergiodj+buildbot
  2016-12-11 10:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01  3:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5486f16481dffa1c1a0d1fd9e38b97e3678078ed ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 5486f16481dffa1c1a0d1fd9e38b97e3678078ed

Use new/delete instead of malloc/free-based functions

The following patches introduce C++ vectors and strings as fields of the
various ui_out structures.  We therefore need to use new/delete so that
their contructor/destructor is called.  I find it simpler to change all
the allocations in a separate preliminary patch, rather than in each
individual patch.

gdb/ChangeLog:

	* cli-out.c (cli_uiout_dtor): Use delete instead of xfree.
	(cli_out_new): Use new instead of XNEW.
	* mi/mi-out.c (mi_out_data_dtor): Use delete instead of xfree.
	(mi_out_new): Use new instead of XNEW.
	* tui/tui-out.c (tui_out_new): Likewise.
	* ui-out.c (push_level): Likewise.
	(pop_level): Use delete instead of xfree.
	(clear_header_list): Use delete instead of xfree.
	(append_header_to_list): Use new instead of XNEW.
	(ui_out_new): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use std::vector for ui_out::levels
@ 2016-12-01  3:47 sergiodj+buildbot
  2016-12-11 15:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01  3:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56df3084847984aeddd8c24ca997242ec8c5a369 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 56df3084847984aeddd8c24ca997242ec8c5a369

Use std::vector for ui_out::levels

Convert the levels field of struct ui_out to be a vector of unique_ptr
to ui_out_level.  This way, the ownership of the ui_out_level objects by
the ui_out instance is clear.

gdb/ChangeLog:

	* ui-out.c (ui_out_level_p): Remove typedef.
	(DEF_VEC_P (ui_out_level_p)): Remove definition.
	(struct ui_out) <levels>: Change type to vector of unique_ptr of
	ui_out_level.
	(current_level): Update.
	(push_level): Update.
	(pop_level): Update, don't manually delete the ui_out_level
	instance.
	(ui_out_new): Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use std::vector for mi_ui_out_data::streams
@ 2016-12-01  4:21 sergiodj+buildbot
  2016-12-11 19:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01  4:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a9d4ea535a6c9b8c2e7cdf91377abe284d0b277 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 4a9d4ea535a6c9b8c2e7cdf91377abe284d0b277

Use std::vector for mi_ui_out_data::streams

Use a standard vector instead of the home-made version.  I used a vector
of plain pointers, because the mi_ui_out_data object doesn't own the
streams objects (i.e. they shouldn't be deleted when the vector is
deleted).

gdb/ChangeLog:

	* mi/mi-out.c: Remove vec.h include.
	(mi_ui_out_data) <streams>: Change type to std::vector.
	(mi_field_string): Update.
	(mi_field_fmt): Update.
	(mi_flush): Update.
	(mi_redirect): Update.
	(field_separator): Update.
	(mi_open): Update.
	(mi_close): Update.
	(mi_out_buffered): Update.
	(mi_out_rewind): Update.
	(mi_out_put): Update.
	(mi_out_data_ctor): Update.
	(mi_out_data_dtor): Don't free streams.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use std::vector for cli_ui_out_data::streams
@ 2016-12-01  5:08 sergiodj+buildbot
  2016-12-11 20:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01  5:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b9b118c3bb29052ee76c6bf32b99962cda5113ba ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: b9b118c3bb29052ee76c6bf32b99962cda5113ba

Use std::vector for cli_ui_out_data::streams

Use a standard vector instead of the home-made version.  I used a vector
of plain pointers, because the cli_ui_out_data object doesn't own the
streams objects (i.e. they shouldn't be deleted when the vector is
deleted).

gdb/ChangeLog:

	* cli-out.h (cli_ui_out_data) <streams>: Change type to
	std::vector.
	* cli-out.c: Remove vec.h include.
	(cli_uiout_dtor): Update.
	(cli_field_fmt): Update.
	(cli_spaces): Update.
	(cli_text): Update.
	(cli_message): Update.
	(cli_flush): Update.
	(cli_redirect): Update.
	(out_field_fmt): Update.
	(field_separator): Update.
	(cli_out_data_ctor): Update.
	(cli_out_new): Update.
	(cli_out_set_stream): Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use std::string in ui_out_table
@ 2016-12-01  5:58 sergiodj+buildbot
  2016-12-11 22:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01  5:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95a23284a3db0ec85bb0b11c70e6b5acf00563f6 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 95a23284a3db0ec85bb0b11c70e6b5acf00563f6

Use std::string in ui_out_table

Use std::string for the id field of the ui_out_table object.

I found that all users of ui_out_table_begin passed a non-NULL value to
the tblid parameter, so we don't have to worry about the NULL case.  I
changed the tblid parameter to be a std::string while at it.

gdb/ChangeLog:

	* ui-out.c (struct ui_out_table) <id>: Change type to
	std::string.
	(ui_out_table_begin): Change tblid parameter type to
	std::string, adapt code.
	update following type change.
	(clear_table): Update.
	(ui_out_new): Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix seg-fault running addr2line on a corrupt binary.
@ 2016-12-01 10:32 sergiodj+buildbot
  2016-12-12  1:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 10:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50455f1ab2935f7321215dfa681745c9b1cb5b19 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 50455f1ab2935f7321215dfa681745c9b1cb5b19

Fix seg-fault running addr2line on a corrupt binary.

	PR binutils/20891
	* aoutx.h (find_nearest_line): Handle the case where the main file
	name and the directory name are both empty.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix abort in x86 disassembler.
@ 2016-12-01 12:11 sergiodj+buildbot
  2016-12-12  4:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 12:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a37a2806e3289294ed214aed3c8a45db46026b39 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: a37a2806e3289294ed214aed3c8a45db46026b39

Fix abort in x86 disassembler.

	PR binutils/20893
	* i386-dis.c (OP_VEX): Replace call to abort with a append of bad
	opcode designator.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix a seg-fault disassembling a corrupt binary.
@ 2016-12-01 12:29 sergiodj+buildbot
  2016-12-12  7:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 12:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e82ab856bb4689330c29fb9f1c57a8555b26380e ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: e82ab856bb4689330c29fb9f1c57a8555b26380e

Fix a seg-fault disassembling a corrupt binary.

	PR binutils/20892
	* aoutx.h (find_nearest_line): Handle the case where the function
	name is empty.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix handling of MIPS16 HI16 relocs.
@ 2016-12-01 13:18 sergiodj+buildbot
  2016-12-12 10:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 13:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40a0bfddf07620f5321927b3231502debb3b73bc ***

Author: Ma Jiang <ma.jiang@zte.com.cn>
Branch: master
Commit: 40a0bfddf07620f5321927b3231502debb3b73bc

Fix handling of MIPS16 HI16 relocs.

	PR ld/16720
	* elfxx-mips.c (mips_elf_calculate_relocation): Remove overflow
	test for HI16 relocs.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix accesses to the GOT for AARCH64 operating in 32-bit mode.
@ 2016-12-01 14:12 sergiodj+buildbot
  2016-12-12 13:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 14:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5cd1d8bcc24e948e86a636161e6d72f6316545a7 ***

Author: Yury Norov <ynorov@caviumnetworks.com>
Branch: master
Commit: 5cd1d8bcc24e948e86a636161e6d72f6316545a7

Fix accesses to the GOT for AARCH64 operating in 32-bit mode.

	PR ld/20868
bfd	* elfnn-aarch64.c (elfNN_aarch64_tls_relax): Use 32-bit accesses
	to the GOT when operating in 32-bit mode.

ld	* testsuite/ld-aarch64/tls-relax-gd-ie-ilp32.d: New test.
	* testsuite/ld-aarch64/relocs-ilp32.ld: Linker script for the new
	test.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix bug with FP stur instructions.
@ 2016-12-01 17:48 sergiodj+buildbot
  2016-12-12 18:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88ddd4a1ef8818984f87f574b424ccdc7db19660 ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: 88ddd4a1ef8818984f87f574b424ccdc7db19660

Fix bug with FP stur instructions.

sim/aarch64
	* simulator.c (fsturs): Switch use of rn and st variables.
	(fsturd, fsturq): Likewise


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase output by basic functions
@ 2016-12-01 21:12 sergiodj+buildbot
  2016-12-12 20:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 21:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc6c7af4a2f23c48a38139fc7e0ed2ac7b12bb69 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: bc6c7af4a2f23c48a38139fc7e0ed2ac7b12bb69

Fix test names starting with uppercase output by basic functions

The following patch is based on the previous patch i sent and handles cases of
test names that start with an uppercase letter. Test names should start with
lowercase unless it starts with the name of a technology, architecture, ISA
etc.

This first patch addresses cases of test names output explicitly via xfail,
kfail, kpass, fail, pass, unsupported, untested and also names set with the
pattern "set test" and "set testname".

gdb/testsuite/ChangeLog:
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names starting with uppercase throughout all the files below.

	* gdb.ada/array_return.exp
	* gdb.ada/catch_ex.exp
	* gdb.ada/info_exc.exp
	* gdb.ada/mi_catch_ex.exp
	* gdb.ada/mi_dyn_arr.exp
	* gdb.ada/mi_ex_cond.exp
	* gdb.ada/mi_exc_info.exp
	* gdb.ada/mi_interface.exp
	* gdb.ada/mi_task_arg.exp
	* gdb.ada/mi_task_info.exp
	* gdb.ada/mi_var_array.exp
	* gdb.arch/alpha-step.exp
	* gdb.arch/amd64-disp-step.exp
	* gdb.arch/arm-disp-step.exp
	* gdb.arch/disp-step-insn-reloc.exp
	* gdb.arch/e500-prologue.exp
	* gdb.arch/ftrace-insn-reloc.exp
	* gdb.arch/gdb1558.exp
	* gdb.arch/i386-bp_permanent.exp
	* gdb.arch/i386-disp-step.exp
	* gdb.arch/i386-float.exp
	* gdb.arch/i386-gnu-cfi.exp
	* gdb.arch/ia64-breakpoint-shadow.exp
	* gdb.arch/mips16-thunks.exp
	* gdb.arch/pa-nullify.exp
	* gdb.arch/powerpc-aix-prologue.exp
	* gdb.arch/powerpc-power.exp
	* gdb.arch/ppc-dfp.exp
	* gdb.arch/s390-tdbregs.exp
	* gdb.arch/spu-info.exp
	* gdb.arch/spu-ls.exp
	* gdb.arch/thumb-bx-pc.exp
	* gdb.base/advance.exp
	* gdb.base/annota-input-while-running.exp
	* gdb.base/arrayidx.exp
	* gdb.base/asmlabel.exp
	* gdb.base/async.exp
	* gdb.base/attach-wait-input.exp
	* gdb.base/auto-connect-native-target.exp
	* gdb.base/batch-preserve-term-settings.exp
	* gdb.base/bfp-test.exp
	* gdb.base/bigcore.exp
	* gdb.base/bp-permanent.exp
	* gdb.base/break-always.exp
	* gdb.base/break-fun-addr.exp
	* gdb.base/break-idempotent.exp
	* gdb.base/break-main-file-remove-fail.exp
	* gdb.base/break-probes.exp
	* gdb.base/break-unload-file.exp
	* gdb.base/break.exp
	* gdb.base/call-ar-st.exp
	* gdb.base/call-rt-st.exp
	* gdb.base/call-sc.exp
	* gdb.base/call-signal-resume.exp
	* gdb.base/call-strs.exp
	* gdb.base/callexit.exp
	* gdb.base/callfuncs.exp
	* gdb.base/catch-gdb-caused-signals.exp
	* gdb.base/catch-signal-siginfo-cond.exp
	* gdb.base/catch-syscall.exp
	* gdb.base/compare-sections.exp
	* gdb.base/cond-eval-mode.exp
	* gdb.base/condbreak-call-false.exp
	* gdb.base/consecutive-step-over.exp
	* gdb.base/cursal.exp
	* gdb.base/disabled-location.exp
	* gdb.base/disasm-end-cu.exp
	* gdb.base/display.exp
	* gdb.base/double-prompt-target-event-error.exp
	* gdb.base/dprintf-bp-same-addr.exp
	* gdb.base/dprintf-detach.exp
	* gdb.base/dprintf-next.exp
	* gdb.base/dprintf-non-stop.exp
	* gdb.base/dprintf-pending.exp
	* gdb.base/dso2dso.exp
	* gdb.base/ending-run.exp
	* gdb.base/enum_cond.exp
	* gdb.base/examine-backward.exp
	* gdb.base/exe-lock.exp
	* gdb.base/exec-invalid-sysroot.exp
	* gdb.base/execl-update-breakpoints.exp
	* gdb.base/execution-termios.exp
	* gdb.base/fileio.exp
	* gdb.base/fixsection.exp
	* gdb.base/foll-exec-mode.exp
	* gdb.base/foll-exec.exp
	* gdb.base/fork-running-state.exp
	* gdb.base/frame-args.exp
	* gdb.base/fullpath-expand.exp
	* gdb.base/func-ptr.exp
	* gdb.base/gcore-relro-pie.exp
	* gdb.base/gdb1090.exp
	* gdb.base/gdb1555.exp
	* gdb.base/global-var-nested-by-dso.exp
	* gdb.base/gnu-ifunc.exp
	* gdb.base/hbreak-in-shr-unsupported.exp
	* gdb.base/hbreak-unmapped.exp
	* gdb.base/hook-stop.exp
	* gdb.base/infcall-input.exp
	* gdb.base/info-fun.exp
	* gdb.base/info-shared.exp
	* gdb.base/interrupt-noterm.exp
	* gdb.base/jit-so.exp
	* gdb.base/jit.exp
	* gdb.base/line-symtabs.exp
	* gdb.base/list.exp
	* gdb.base/longjmp.exp
	* gdb.base/macscp.exp
	* gdb.base/max-value-size.exp
	* gdb.base/nodebug.exp
	* gdb.base/nofield.exp
	* gdb.base/overlays.exp
	* gdb.base/paginate-after-ctrl-c-running.exp
	* gdb.base/paginate-bg-execution.exp
	* gdb.base/paginate-inferior-exit.exp
	* gdb.base/pending.exp
	* gdb.base/pr11022.exp
	* gdb.base/printcmds.exp
	* gdb.base/ptr-typedef.exp
	* gdb.base/ptype.exp
	* gdb.base/randomize.exp
	* gdb.base/range-stepping.exp
	* gdb.base/realname-expand.exp
	* gdb.base/relativedebug.exp
	* gdb.base/remote.exp
	* gdb.base/savedregs.exp
	* gdb.base/sepdebug.exp
	* gdb.base/set-noassign.exp
	* gdb.base/shlib-call.exp
	* gdb.base/shreloc.exp
	* gdb.base/sigaltstack.exp
	* gdb.base/sigbpt.exp
	* gdb.base/siginfo-addr.exp
	* gdb.base/siginfo-obj.exp
	* gdb.base/siginfo-thread.exp
	* gdb.base/signest.exp
	* gdb.base/signull.exp
	* gdb.base/sigrepeat.exp
	* gdb.base/skip.exp
	* gdb.base/so-impl-ld.exp
	* gdb.base/solib-corrupted.exp
	* gdb.base/solib-disc.exp
	* gdb.base/solib-display.exp
	* gdb.base/solib-overlap.exp
	* gdb.base/solib-search.exp
	* gdb.base/solib-symbol.exp
	* gdb.base/source-execution.exp
	* gdb.base/sss-bp-on-user-bp-2.exp
	* gdb.base/sss-bp-on-user-bp.exp
	* gdb.base/stack-checking.exp
	* gdb.base/stale-infcall.exp
	* gdb.base/step-break.exp
	* gdb.base/step-line.exp
	* gdb.base/step-over-exit.exp
	* gdb.base/step-test.exp
	* gdb.base/structs.exp
	* gdb.base/sym-file.exp
	* gdb.base/symtab-search-order.exp
	* gdb.base/term.exp
	* gdb.base/type-opaque.exp
	* gdb.base/unload.exp
	* gdb.base/until-nodebug.exp
	* gdb.base/until.exp
	* gdb.base/unwindonsignal.exp
	* gdb.base/watch-cond.exp
	* gdb.base/watch-non-mem.exp
	* gdb.base/watch_thread_num.exp
	* gdb.base/watchpoint-reuse-slot.exp
	* gdb.base/watchpoint-solib.exp
	* gdb.base/watchpoint.exp
	* gdb.btrace/dlopen.exp
	* gdb.cell/arch.exp
	* gdb.cell/break.exp
	* gdb.cell/bt.exp
	* gdb.cell/core.exp
	* gdb.cell/data.exp
	* gdb.cell/dwarfaddr.exp
	* gdb.cell/ea-cache.exp
	* gdb.cell/ea-standalone.exp
	* gdb.cell/ea-test.exp
	* gdb.cell/f-regs.exp
	* gdb.cell/fork.exp
	* gdb.cell/gcore.exp
	* gdb.cell/mem-access.exp
	* gdb.cell/ptype.exp
	* gdb.cell/registers.exp
	* gdb.cell/sizeof.exp
	* gdb.cell/solib-symbol.exp
	* gdb.cell/solib.exp
	* gdb.compile/compile-tls.exp
	* gdb.cp/exception.exp
	* gdb.cp/gdb2495.exp
	* gdb.cp/local.exp
	* gdb.cp/mb-inline.exp
	* gdb.cp/mb-templates.exp
	* gdb.cp/pr10687.exp
	* gdb.cp/pr9167.exp
	* gdb.cp/scope-err.exp
	* gdb.cp/templates.exp
	* gdb.cp/virtfunc.exp
	* gdb.dwarf2/dw2-dir-file-name.exp
	* gdb.dwarf2/dw2-single-line-discriminators.exp
	* gdb.fortran/complex.exp
	* gdb.fortran/library-module.exp
	* gdb.guile/guile.exp
	* gdb.guile/scm-cmd.exp
	* gdb.guile/scm-frame-inline.exp
	* gdb.guile/scm-objfile.exp
	* gdb.guile/scm-pretty-print.exp
	* gdb.guile/scm-symbol.exp
	* gdb.guile/scm-type.exp
	* gdb.guile/scm-value.exp
	* gdb.linespec/keywords.exp
	* gdb.linespec/ls-errs.exp
	* gdb.linespec/macro-relative.exp
	* gdb.linespec/thread.exp
	* gdb.mi/mi-breakpoint-changed.exp
	* gdb.mi/mi-dprintf-pending.exp
	* gdb.mi/mi-fullname-deleted.exp
	* gdb.mi/mi-logging.exp
	* gdb.mi/mi-pending.exp
	* gdb.mi/mi-solib.exp
	* gdb.mi/new-ui-mi-sync.exp
	* gdb.mi/user-selected-context-sync.exp
	* gdb.multi/dummy-frame-restore.exp
	* gdb.multi/multi-arch-exec.exp
	* gdb.multi/remove-inferiors.exp
	* gdb.multi/watchpoint-multi-exit.exp
	* gdb.opt/solib-intra-step.exp
	* gdb.perf/backtrace.exp
	* gdb.perf/single-step.exp
	* gdb.perf/skip-command.exp
	* gdb.perf/skip-prologue.exp
	* gdb.perf/solib.exp
	* gdb.python/lib-types.exp
	* gdb.python/py-as-string.exp
	* gdb.python/py-bad-printers.exp
	* gdb.python/py-block.exp
	* gdb.python/py-breakpoint.exp
	* gdb.python/py-cmd.exp
	* gdb.python/py-events.exp
	* gdb.python/py-evthreads.exp
	* gdb.python/py-finish-breakpoint.exp
	* gdb.python/py-finish-breakpoint2.exp
	* gdb.python/py-frame-inline.exp
	* gdb.python/py-frame.exp
	* gdb.python/py-inferior.exp
	* gdb.python/py-infthread.exp
	* gdb.python/py-mi.exp
	* gdb.python/py-objfile.exp
	* gdb.python/py-pp-maint.exp
	* gdb.python/py-pp-registration.exp
	* gdb.python/py-prettyprint.exp
	* gdb.python/py-recurse-unwind.exp
	* gdb.python/py-shared.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-symtab.exp
	* gdb.python/py-template.exp
	* gdb.python/py-type.exp
	* gdb.python/py-unwind-maint.exp
	* gdb.python/py-unwind.exp
	* gdb.python/py-value.exp
	* gdb.python/python.exp
	* gdb.reverse/finish-reverse-bkpt.exp
	* gdb.reverse/insn-reverse.exp
	* gdb.reverse/next-reverse-bkpt-over-sr.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/solib-reverse.exp
	* gdb.stabs/gdb11479.exp
	* gdb.stabs/weird.exp
	* gdb.threads/fork-child-threads.exp
	* gdb.threads/fork-plus-threads.exp
	* gdb.threads/fork-thread-pending.exp
	* gdb.threads/forking-threads-plus-breakpoint.exp
	* gdb.threads/hand-call-in-threads.exp
	* gdb.threads/interrupted-hand-call.exp
	* gdb.threads/linux-dp.exp
	* gdb.threads/local-watch-wrong-thread.exp
	* gdb.threads/next-while-other-thread-longjmps.exp
	* gdb.threads/non-ldr-exit.exp
	* gdb.threads/pending-step.exp
	* gdb.threads/print-threads.exp
	* gdb.threads/process-dies-while-detaching.exp
	* gdb.threads/process-dies-while-handling-bp.exp
	* gdb.threads/pthreads.exp
	* gdb.threads/queue-signal.exp
	* gdb.threads/reconnect-signal.exp
	* gdb.threads/signal-command-handle-nopass.exp
	* gdb.threads/signal-command-multiple-signals-pending.exp
	* gdb.threads/signal-delivered-right-thread.exp
	* gdb.threads/signal-sigtrap.exp
	* gdb.threads/sigthread.exp
	* gdb.threads/staticthreads.exp
	* gdb.threads/stepi-random-signal.exp
	* gdb.threads/thread-unwindonsignal.exp
	* gdb.threads/thread_check.exp
	* gdb.threads/thread_events.exp
	* gdb.threads/tid-reuse.exp
	* gdb.threads/tls-nodebug.exp
	* gdb.threads/tls-shared.exp
	* gdb.threads/tls-so_extern.exp
	* gdb.threads/tls.exp
	* gdb.threads/wp-replication.exp
	* gdb.trace/actions-changed.exp
	* gdb.trace/actions.exp
	* gdb.trace/backtrace.exp
	* gdb.trace/change-loc.exp
	* gdb.trace/collection.exp
	* gdb.trace/deltrace.exp
	* gdb.trace/disconnected-tracing.exp
	* gdb.trace/entry-values.exp
	* gdb.trace/ftrace-lock.exp
	* gdb.trace/ftrace.exp
	* gdb.trace/infotrace.exp
	* gdb.trace/mi-trace-frame-collected.exp
	* gdb.trace/mi-trace-unavailable.exp
	* gdb.trace/mi-traceframe-changed.exp
	* gdb.trace/mi-tracepoint-changed.exp
	* gdb.trace/mi-tsv-changed.exp
	* gdb.trace/no-attach-trace.exp
	* gdb.trace/packetlen.exp
	* gdb.trace/passc-dyn.exp
	* gdb.trace/passcount.exp
	* gdb.trace/pending.exp
	* gdb.trace/pr16508.exp
	* gdb.trace/qtro.exp
	* gdb.trace/range-stepping.exp
	* gdb.trace/read-memory.exp
	* gdb.trace/report.exp
	* gdb.trace/save-trace.exp
	* gdb.trace/signal.exp
	* gdb.trace/stap-trace.exp
	* gdb.trace/status-stop.exp
	* gdb.trace/strace.exp
	* gdb.trace/tfile.exp
	* gdb.trace/tfind.exp
	* gdb.trace/trace-break.exp
	* gdb.trace/trace-condition.exp
	* gdb.trace/trace-enable-disable.exp
	* gdb.trace/trace-mt.exp
	* gdb.trace/tracecmd.exp
	* gdb.trace/tracefile-pseudo-reg.exp
	* gdb.trace/tspeed.exp
	* gdb.trace/tstatus.exp
	* gdb.trace/tsv.exp
	* gdb.trace/unavailable.exp
	* gdb.trace/while-dyn.exp
	* gdb.trace/while-stepping.exp
	* lib/gdb-guile.exp
	* lib/gdb.exp
	* lib/mi-support.exp
	* lib/pascal.exp
	* lib/perftest.exp
	* lib/prelink-support.exp
	* lib/selftest-support.exp


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase using gdb_test on a single line.
@ 2016-12-01 21:50 sergiodj+buildbot
  2016-12-12 23:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cdc7edd7b17dddd3558bd04d9b2fb5a73dc75f1c ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: cdc7edd7b17dddd3558bd04d9b2fb5a73dc75f1c

Fix test names starting with uppercase using gdb_test on a single line.

Changes in v3:
  Fixed incorrect substitutions.

This fixes offender testcases that have test names starting with uppercase
when using gdb_test in a single line construct.

gdb/testsuite/ChangeLog
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names starting with uppercase throughout the files.

	* gdb.arch/i386-mpx-simple_segv.exp
	* gdb.arch/i386-mpx.exp
	* gdb.arch/i386-permbkpt.exp
	* gdb.arch/pa-nullify.exp
	* gdb.arch/powerpc-d128-regs.exp
	* gdb.arch/vsx-regs.exp
	* gdb.base/bfp-test.exp
	* gdb.base/break.exp
	* gdb.base/breakpoint-shadow.exp
	* gdb.base/callfuncs.exp
	* gdb.base/charset.exp
	* gdb.base/commands.exp
	* gdb.base/completion.exp
	* gdb.base/dfp-test.exp
	* gdb.base/echo.exp
	* gdb.base/ending-run.exp
	* gdb.base/eval.exp
	* gdb.base/expand-psymtabs.exp
	* gdb.base/float128.exp
	* gdb.base/floatn.exp
	* gdb.base/foll-exec-mode.exp
	* gdb.base/gdb1056.exp
	* gdb.base/gdb11531.exp
	* gdb.base/kill-after-signal.exp
	* gdb.base/multi-forks.exp
	* gdb.base/overlays.exp
	* gdb.base/pending.exp
	* gdb.base/sepdebug.exp
	* gdb.base/testenv.exp
	* gdb.base/valgrind-db-attach.exp
	* gdb.base/watch_thread_num.exp
	* gdb.base/watchpoint-cond-gone.exp
	* gdb.base/watchpoint.exp
	* gdb.base/watchpoints.exp
	* gdb.cp/arg-reference.exp
	* gdb.cp/baseenum.exp
	* gdb.cp/operator.exp
	* gdb.cp/shadow.exp
	* gdb.dwarf2/dw2-op-out-param.exp
	* gdb.dwarf2/dw2-reg-undefined.exp
	* gdb.go/chan.exp
	* gdb.go/hello.exp
	* gdb.go/integers.exp
	* gdb.go/methods.exp
	* gdb.go/package.exp
	* gdb.guile/scm-parameter.exp
	* gdb.guile/scm-progspace.exp
	* gdb.guile/scm-value.exp
	* gdb.mi/mi-pending.exp
	* gdb.mi/user-selected-context-sync.exp
	* gdb.multi/multi-attach.exp
	* gdb.multi/tids.exp
	* gdb.opt/clobbered-registers-O2.exp
	* gdb.pascal/floats.exp
	* gdb.pascal/integers.exp
	* gdb.python/py-block.exp
	* gdb.python/py-events.exp
	* gdb.python/py-parameter.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-symtab.exp
	* gdb.python/py-type.exp
	* gdb.python/py-value.exp
	* gdb.python/py-xmethods.exp
	* gdb.python/python.exp
	* gdb.reverse/break-precsave.exp
	* gdb.reverse/consecutive-precsave.exp
	* gdb.reverse/finish-precsave.exp
	* gdb.reverse/i386-precsave.exp
	* gdb.reverse/machinestate-precsave.exp
	* gdb.reverse/sigall-precsave.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/step-precsave.exp
	* gdb.reverse/until-precsave.exp
	* gdb.reverse/watch-precsave.exp
	* gdb.server/ext-attach.exp
	* gdb.server/ext-restart.exp
	* gdb.server/ext-run.exp
	* gdb.server/ext-wrapper.exp
	* gdb.stabs/gdb11479.exp
	* gdb.stabs/weird.exp
	* gdb.threads/attach-many-short-lived-threads.exp
	* gdb.threads/kill.exp
	* gdb.threads/watchpoint-fork.exp


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase using gdb_test_no_output
@ 2016-12-01 22:09 sergiodj+buildbot
  2016-12-13  2:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 22:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f058c10cef5987ee1f1cb28c9a8cf5ef1ec4d11 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 9f058c10cef5987ee1f1cb28c9a8cf5ef1ec4d11

Fix test names starting with uppercase using gdb_test_no_output

This fixes offender testcases that have test names starting with uppercase
when using gdb_test_no_output in a single-line construct.

gdb/testsuite/ChangeLog
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names starting with uppercase throughout the files.

	* gdb.base/charset.exp
	* gdb.base/eval.exp
	* gdb.base/multi-forks.exp
	* gdb.guile/scm-progspace.exp
	* gdb.opencl/datatypes.exp
	* gdb.python/py-block.exp
	* gdb.python/py-function.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-symtab.exp
	* gdb.python/py-xmethods.exp
	* gdb.reverse/break-precsave.exp
	* gdb.reverse/break-reverse.exp
	* gdb.reverse/consecutive-precsave.exp
	* gdb.reverse/consecutive-reverse.exp
	* gdb.reverse/finish-precsave.exp
	* gdb.reverse/finish-reverse-bkpt.exp
	* gdb.reverse/finish-reverse.exp
	* gdb.reverse/fstatat-reverse.exp
	* gdb.reverse/getresuid-reverse.exp
	* gdb.reverse/i386-precsave.exp
	* gdb.reverse/i386-reverse.exp
	* gdb.reverse/i386-sse-reverse.exp
	* gdb.reverse/i387-stack-reverse.exp
	* gdb.reverse/insn-reverse.exp
	* gdb.reverse/machinestate-precsave.exp
	* gdb.reverse/machinestate.exp
	* gdb.reverse/next-reverse-bkpt-over-sr.exp
	* gdb.reverse/pipe-reverse.exp
	* gdb.reverse/readv-reverse.exp
	* gdb.reverse/recvmsg-reverse.exp
	* gdb.reverse/rerun-prec.exp
	* gdb.reverse/s390-mvcle.exp
	* gdb.reverse/sigall-precsave.exp
	* gdb.reverse/sigall-reverse.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/solib-reverse.exp
	* gdb.reverse/step-precsave.exp
	* gdb.reverse/step-reverse.exp
	* gdb.reverse/time-reverse.exp
	* gdb.reverse/until-precsave.exp
	* gdb.reverse/until-reverse.exp
	* gdb.reverse/waitpid-reverse.exp
	* gdb.reverse/watch-precsave.exp
	* gdb.reverse/watch-reverse.exp


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase using gdb_test_multiple
@ 2016-12-01 23:01 sergiodj+buildbot
  2016-12-13  5:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 23:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de97fdd4a05cd7ad0b05444f1721f26c1ad9322f ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: de97fdd4a05cd7ad0b05444f1721f26c1ad9322f

Fix test names starting with uppercase using gdb_test_multiple

This fixes offender testcases that have test names starting with uppercase
when using gdb_test_multiple in a single-line construct.

gdb/testsuite/ChangeLog
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names starting with uppercase throughout the files.

	* gdb.arch/i386-bp_permanent.exp
	* gdb.arch/i386-gnu-cfi.exp
	* gdb.base/disasm-end-cu.exp
	* gdb.base/macscp.exp
	* gdb.base/pending.exp
	* gdb.base/watch_thread_num.exp
	* gdb.cp/exception.exp
	* gdb.cp/gdb2495.exp
	* gdb.cp/local.exp
	* gdb.python/py-evsignal.exp
	* gdb.python/python.exp
	* gdb.trace/tracecmd.exp


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase using multi-line gdb_test/mi_gdb_test
@ 2016-12-01 23:25 sergiodj+buildbot
  2016-12-13  8:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 23:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb95117e107fe58ecd35683bf0e8da3b414378ff ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: bb95117e107fe58ecd35683bf0e8da3b414378ff

Fix test names starting with uppercase using multi-line gdb_test/mi_gdb_test

This fixes offender testcases that have test names starting with uppercase
when using gdb_test/mi_gdb_test in a multi-line construct.

gdb/testsuite/ChangeLog
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names starting with uppercase throughout the files.

	* gdb.ada/array_return.exp
	* gdb.ada/expr_delims.exp
	* gdb.ada/mi_dyn_arr.exp
	* gdb.ada/mi_interface.exp
	* gdb.ada/mi_var_array.exp
	* gdb.ada/watch_arg.exp
	* gdb.arch/alpha-step.exp
	* gdb.arch/altivec-regs.exp
	* gdb.arch/e500-regs.exp
	* gdb.arch/powerpc-d128-regs.exp
	* gdb.base/arrayidx.exp
	* gdb.base/break.exp
	* gdb.base/checkpoint.exp
	* gdb.base/debug-expr.exp
	* gdb.base/dmsym.exp
	* gdb.base/radix.exp
	* gdb.base/sepdebug.exp
	* gdb.base/testenv.exp
	* gdb.base/watch_thread_num.exp
	* gdb.base/watchpoint-cond-gone.exp
	* gdb.cell/break.exp
	* gdb.cell/ea-cache.exp
	* gdb.compile/compile.exp
	* gdb.cp/gdb2495.exp
	* gdb.gdb/selftest.exp
	* gdb.gdb/xfullpath.exp
	* gdb.go/hello.exp
	* gdb.go/integers.exp
	* gdb.objc/basicclass.exp
	* gdb.pascal/hello.exp
	* gdb.pascal/integers.exp
	* gdb.python/py-breakpoint.exp
	* gdb.python/py-cmd.exp
	* gdb.python/py-linetable.exp
	* gdb.python/py-xmethods.exp
	* gdb.python/python.exp
	* gdb.reverse/consecutive-precsave.exp
	* gdb.reverse/finish-precsave.exp
	* gdb.reverse/i386-precsave.exp
	* gdb.reverse/machinestate-precsave.exp
	* gdb.reverse/sigall-precsave.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/step-precsave.exp
	* gdb.reverse/until-precsave.exp
	* gdb.reverse/watch-precsave.exp
	* gdb.threads/leader-exit.exp
	* gdb.threads/pthreads.exp
	* gdb.threads/wp-replication.exp
	* gdb.trace/actions.exp
	* gdb.trace/mi-tsv-changed.exp
	* gdb.trace/tsv.exp


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase using multi-line gdb_test_no_output
@ 2016-12-02  0:06 sergiodj+buildbot
  2016-12-13 11:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  0:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd2ddb6cde55a20d191e1002dbe1977df695cda9 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: cd2ddb6cde55a20d191e1002dbe1977df695cda9

Fix test names starting with uppercase using multi-line gdb_test_no_output

This fixes offender testcases that have test names starting with uppercase
when using gdb_test_no_output in a multi-line construct.

gdb/testsuite/ChangeLog
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names starting with uppercase throughout the files.

	* gdb.ada/assign_1.exp
	* gdb.ada/boolean_expr.exp
	* gdb.base/arrayidx.exp
	* gdb.base/del.exp
	* gdb.base/gcore-buffer-overflow.exp
	* gdb.base/testenv.exp
	* gdb.compile/compile.exp
	* gdb.python/py-framefilter-invalidarg.exp
	* gdb.python/py-framefilter.exp


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase using multi-line gdb_test_multiple
@ 2016-12-02  0:34 sergiodj+buildbot
  2016-12-13 13:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  0:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb9feb35913d4cf26baf01e1638b18af301f5387 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: fb9feb35913d4cf26baf01e1638b18af301f5387

Fix test names starting with uppercase using multi-line gdb_test_multiple

This fixes offender testcases that have test names starting with uppercase
when using gdb_test_multiple in a multi-line construct.

gdb/testsuite/ChangeLog
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.cp/gdb2495.exp: Replace gdb_test_multiple
	with gdb_test_no_output.
	Use command as test name.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fixup testcases outputting own name as a test name and standardize failed compilation messages
@ 2016-12-02  1:27 sergiodj+buildbot
  2016-12-13 17:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  1:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 84c93cd5f1ff869eb8c04314738eaa2cddb3c29e ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 84c93cd5f1ff869eb8c04314738eaa2cddb3c29e

Fixup testcases outputting own name as a test name and standardize failed compilation messages

Changes in v3:

- Adjusted some testcases where the message "failed to compile" was not unique.

Changes in v2:

- Addressed comments from reviewers.
- Fixed spurious whitespaces.
- Changed compilation failure messages that included source/binary paths to
  ones that are short and deterministic.

---

Another bit of cleanup to the testsuite. We have a number of tests that are
not honoring the rule of not outputting their own name as a test name.

I fixed up all the offenders i could find with the following regular
expression:

"(xfail|kfail|kpass|fail|pass|unsupported|untested) ([A-Za-z0-9]+|\\\$(.)*testfile(.)*)\.exp$"

gdb/testsuite/ChangeLog:
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names and standardize compilation error messages throughout
	the following files:

	* gdb.ada/start.exp
	* gdb.arch/alpha-step.exp
	* gdb.arch/e500-prologue.exp
	* gdb.arch/ftrace-insn-reloc.exp
	* gdb.arch/gdb1291.exp
	* gdb.arch/gdb1431.exp
	* gdb.arch/gdb1558.exp
	* gdb.arch/i386-dr3-watch.exp
	* gdb.arch/i386-sse-stack-align.exp
	* gdb.arch/ia64-breakpoint-shadow.exp
	* gdb.arch/pa-nullify.exp
	* gdb.arch/powerpc-aix-prologue.exp
	* gdb.arch/thumb-bx-pc.exp
	* gdb.base/annota1.exp
	* gdb.base/annota3.exp
	* gdb.base/arrayidx.exp
	* gdb.base/assign.exp
	* gdb.base/attach.exp
	* gdb.base/auxv.exp
	* gdb.base/bang.exp
	* gdb.base/bfp-test.exp
	* gdb.base/bigcore.exp
	* gdb.base/bitfields2.exp
	* gdb.base/break-fun-addr.exp
	* gdb.base/break-probes.exp
	* gdb.base/call-rt-st.exp
	* gdb.base/callexit.exp
	* gdb.base/catch-fork-kill.exp
	* gdb.base/charset.exp
	* gdb.base/checkpoint.exp
	* gdb.base/comprdebug.exp
	* gdb.base/constvars.exp
	* gdb.base/coredump-filter.exp
	* gdb.base/cursal.exp
	* gdb.base/cvexpr.exp
	* gdb.base/detach.exp
	* gdb.base/display.exp
	* gdb.base/dmsym.exp
	* gdb.base/dprintf-pending.exp
	* gdb.base/dso2dso.exp
	* gdb.base/dtrace-probe.exp
	* gdb.base/dump.exp
	* gdb.base/enum_cond.exp
	* gdb.base/exe-lock.exp
	* gdb.base/exec-invalid-sysroot.exp
	* gdb.base/execl-update-breakpoints.exp
	* gdb.base/exprs.exp
	* gdb.base/fileio.exp
	* gdb.base/find.exp
	* gdb.base/finish.exp
	* gdb.base/fixsection.exp
	* gdb.base/foll-vfork.exp
	* gdb.base/frame-args.exp
	* gdb.base/gcore.exp
	* gdb.base/gdb1250.exp
	* gdb.base/global-var-nested-by-dso.exp
	* gdb.base/gnu-ifunc.exp
	* gdb.base/hashline1.exp
	* gdb.base/hashline2.exp
	* gdb.base/hashline3.exp
	* gdb.base/hbreak-in-shr-unsupported.exp
	* gdb.base/huge.exp
	* gdb.base/infcall-input.exp
	* gdb.base/info-fun.exp
	* gdb.base/info-shared.exp
	* gdb.base/jit-simple.exp
	* gdb.base/jit-so.exp
	* gdb.base/jit.exp
	* gdb.base/jump.exp
	* gdb.base/label.exp
	* gdb.base/lineinc.exp
	* gdb.base/logical.exp
	* gdb.base/longjmp.exp
	* gdb.base/macscp.exp
	* gdb.base/miscexprs.exp
	* gdb.base/new-ui-echo.exp
	* gdb.base/new-ui-pending-input.exp
	* gdb.base/new-ui.exp
	* gdb.base/nodebug.exp
	* gdb.base/nofield.exp
	* gdb.base/offsets.exp
	* gdb.base/overlays.exp
	* gdb.base/pending.exp
	* gdb.base/pointers.exp
	* gdb.base/pr11022.exp
	* gdb.base/printcmds.exp
	* gdb.base/prologue.exp
	* gdb.base/ptr-typedef.exp
	* gdb.base/realname-expand.exp
	* gdb.base/relativedebug.exp
	* gdb.base/relocate.exp
	* gdb.base/remote.exp
	* gdb.base/reread.exp
	* gdb.base/return2.exp
	* gdb.base/savedregs.exp
	* gdb.base/sep.exp
	* gdb.base/sepdebug.exp
	* gdb.base/sepsymtab.exp
	* gdb.base/set-inferior-tty.exp
	* gdb.base/setshow.exp
	* gdb.base/shlib-call.exp
	* gdb.base/sigaltstack.exp
	* gdb.base/siginfo-addr.exp
	* gdb.base/signals.exp
	* gdb.base/signull.exp
	* gdb.base/sigrepeat.exp
	* gdb.base/so-impl-ld.exp
	* gdb.base/solib-display.exp
	* gdb.base/solib-overlap.exp
	* gdb.base/solib-search.exp
	* gdb.base/solib-symbol.exp
	* gdb.base/structs.exp
	* gdb.base/structs2.exp
	* gdb.base/symtab-search-order.exp
	* gdb.base/twice.exp
	* gdb.base/unload.exp
	* gdb.base/varargs.exp
	* gdb.base/watchpoint-solib.exp
	* gdb.base/watchpoint.exp
	* gdb.base/whatis.exp
	* gdb.base/wrong_frame_bt_full.exp
	* gdb.btrace/dlopen.exp
	* gdb.cell/ea-standalone.exp
	* gdb.cell/ea-test.exp
	* gdb.cp/dispcxx.exp
	* gdb.cp/gdb2384.exp
	* gdb.cp/method2.exp
	* gdb.cp/nextoverthrow.exp
	* gdb.cp/pr10728.exp
	* gdb.disasm/am33.exp
	* gdb.disasm/h8300s.exp
	* gdb.disasm/mn10300.exp
	* gdb.disasm/sh3.exp
	* gdb.dwarf2/dw2-dir-file-name.exp
	* gdb.fortran/complex.exp
	* gdb.fortran/library-module.exp
	* gdb.guile/scm-pretty-print.exp
	* gdb.guile/scm-symbol.exp
	* gdb.guile/scm-type.exp
	* gdb.guile/scm-value.exp
	* gdb.linespec/linespec.exp
	* gdb.mi/gdb701.exp
	* gdb.mi/gdb792.exp
	* gdb.mi/mi-breakpoint-changed.exp
	* gdb.mi/mi-dprintf-pending.exp
	* gdb.mi/mi-dprintf.exp
	* gdb.mi/mi-exit-code.exp
	* gdb.mi/mi-pending.exp
	* gdb.mi/mi-solib.exp
	* gdb.mi/new-ui-mi-sync.exp
	* gdb.mi/pr11022.exp
	* gdb.mi/user-selected-context-sync.exp
	* gdb.opt/solib-intra-step.exp
	* gdb.python/py-events.exp
	* gdb.python/py-finish-breakpoint.exp
	* gdb.python/py-mi.exp
	* gdb.python/py-prettyprint.exp
	* gdb.python/py-shared.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-template.exp
	* gdb.python/py-type.exp
	* gdb.python/py-value.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/solib-reverse.exp
	* gdb.server/solib-list.exp
	* gdb.stabs/weird.exp
	* gdb.threads/reconnect-signal.exp
	* gdb.threads/stepi-random-signal.exp
	* gdb.trace/actions.exp
	* gdb.trace/ax.exp
	* gdb.trace/backtrace.exp
	* gdb.trace/change-loc.exp
	* gdb.trace/deltrace.exp
	* gdb.trace/ftrace-lock.exp
	* gdb.trace/ftrace.exp
	* gdb.trace/infotrace.exp
	* gdb.trace/mi-tracepoint-changed.exp
	* gdb.trace/packetlen.exp
	* gdb.trace/passcount.exp
	* gdb.trace/pending.exp
	* gdb.trace/range-stepping.exp
	* gdb.trace/report.exp
	* gdb.trace/stap-trace.exp
	* gdb.trace/tfind.exp
	* gdb.trace/trace-break.exp
	* gdb.trace/trace-condition.exp
	* gdb.trace/trace-enable-disable.exp
	* gdb.trace/trace-mt.exp
	* gdb.trace/tracecmd.exp
	* gdb.trace/tspeed.exp
	* gdb.trace/tsv.exp
	* lib/perftest.exp


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Replace hand-made linked list of ui_out_hdr by vector and iterator
@ 2016-12-02  2:11 sergiodj+buildbot
  2016-12-13 20:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  2:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 78afa7f8599e46eb94a93510b383dfb35e549f7e ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 78afa7f8599e46eb94a93510b383dfb35e549f7e

Replace hand-made linked list of ui_out_hdr by vector and iterator

Instead of keeping pointers to first, last and current ui_out_hdr in
ui_out_table, we can use an std::vector and an iterator.  Direct random
access of to vector helps make get_next_header a bit nicer by avoiding
iterating on all the headers.  append_header_to_list is also a bit
simpler.

Also, using unique_ptr inside the vector allows expressing the ownership
of the ui_out_hdr objects by the ui_out_table object, and it simplifies
the destruction.

gdb/ChangeLog:

	* ui-out.c (struct ui_out_hdr) <next>: Remove.
	(struct ui_out_table) <header_first, header_last, header_next>: Remove.
	<headers, headers_iterator>: New fields.
	(ui_out_table_body): Update for the new data structure.
	(ui_out_begin): Likewise.
	(clear_header_list): Likewise.
	(append_header_to_list): Likewise.
	(get_next_header): Likewise.
	(ui_out_query_field): Likewise.
	(ui_out_new): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use std::string for ui_out_hdr's text fields
@ 2016-12-02  2:20 sergiodj+buildbot
  2016-12-13 22:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  2:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5209615263fd0444da28cdfb6661ad287909a70 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: c5209615263fd0444da28cdfb6661ad287909a70

Use std::string for ui_out_hdr's text fields

This patch makes ui_out_hdr use std::string for its text fields.  It
makes freeing automatic when the object is deleted.

gdb/ChangeLog:

	* mi/mi-out.c (mi_table_header): Change char * args to
	std::string.
	* cli-out.c (cli_table_header): Likewise.
	* ui-out.h (table_header_ftype): Likewise.
	(ui_out_table_header): Constify colhdr argument.
	(ui_out_query_field): Constify col_name argument.
	* ui-out.c (ui_out_hdr) <col_name, colhdr>: Change type to
	std::string.
	(uo_table_header): Change char * args to std::string.
	(ui_out_table_header): Likewise.
	(get_next_header): Constify colhdr argument and adapt.
	(clear_header_list): Don't free col_name/colhdr fields.
	(append_header_to_list): Change char * args to std::string and
	adapt.
	(verify_field): Constify variable.
	(ui_out_query_field): Constify col_name argument and adapt.
	* breakpoint.c (wrap_indent_at_field): Constify variable.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Class-ify ui_out_hdr
@ 2016-12-02  2:49 sergiodj+buildbot
  2016-12-14  1:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  2:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37e20dd6599203c4e261fc3a2e86711c90cbbed9 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 37e20dd6599203c4e261fc3a2e86711c90cbbed9

Class-ify ui_out_hdr

This patch makes ui_out_hdr (the object that represents an ui-out table
header) a proper C++ class.  No behavior changes, it's all about
encapsulation.

gdb/ChangeLog:

	* ui-out.c (struct ui_out_hdr): Replace with ...
	(class ui_out_hdr): ... this.
	(append_header_to_list): Update.
	(get_next_header): Update.
	(ui_out_query_field): Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Class-ify ui_out_level
@ 2016-12-02  3:57 sergiodj+buildbot
  2016-12-14  4:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  3:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 909c0aa5824080c287b390f82726cf5bfb7011e3 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 909c0aa5824080c287b390f82726cf5bfb7011e3

Class-ify ui_out_level

This patch changes struct ui_out_level to be a real C++ class.  No
behavioral changes.

gdb/ChangeLog:

	* ui-out.c (struct ui_out_level): Replace with ...
	(class ui_out_level): ... this.
	(current_level): Update.
	(push_level): Update.
	(pop_level): Update.
	(verify_field): Update.
	(ui_out_new): Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Simplify ui-out level code
@ 2016-12-02  4:41 sergiodj+buildbot
  2016-12-14  6:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  4:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33b2fac610fff1255a24763277a4bf77f1b59ef1 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 33b2fac610fff1255a24763277a4bf77f1b59ef1

Simplify ui-out level code

Now that we use a vector to store the levels, we don't have to keep a
separate level field in ui_out to keep track of the current level.  We
can efficiently derive it from the vector size.  That causes a little
change in the meaning of the level, as in they are now 1-based instead
of 0-based (the initial level has the "id" 1 now), but it shouldn't
change anything in the behavior.

Additionally, push_level and pop_level don't really need to return the
new level, making them return void simplifies the code a bit.

Finally, the ui_out_begin/ui_out_end callbacks in the ui_out_impl
interface don't need to be passed the level, it's never actually used.

New in v2:

 - Remove or update stale comments.

gdb/ChangeLog:

	* ui-out.h (ui_out_begin_ftype): Remove level parameter.
	(ui_out_end_ftype): Likewise.
	* ui-out.c (struct ui_out) <level>: Replace field with a method
	that dynamically computes the result.
	(current_level): Get vector's back item instead of using
	uiout->level.
	(push_level): Make return type void.
	(pop_level): Make return type void and update access to
	ui_out::level.
	(uo_begin): Remove level parameter.
	(uo_end): Likewise.
	(ui_out_table_begin): Update access to uiout::level.
	(ui_out_begin): Don't read return value from push_level, call
	uiout->level() instead, update call to uo_begin.
	(ui_out_end): Don't read return value from pop_level, update
	call to uo_end.
	(verify_field): Update access to uiout->level.
	(ui_out_new): Don't initialize ui_out::level, call push_level
	to push the initial level instead of doing it by hand.
	* cli-out.c (cli_begin): Remove level parameter.
	(cli_end): Likewise.
	* mi/mi-out.c (mi_begin): Likewise.
	(mi_end): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] ui_out_table: Replace boolean flag with enum
@ 2016-12-02  5:00 sergiodj+buildbot
  2016-12-14  9:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  5:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77a179e77b38161e461f5e37512f0b3fc3582181 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 77a179e77b38161e461f5e37512f0b3fc3582181

ui_out_table: Replace boolean flag with enum

This patch is just a little cleanup, it replaces the body_flag field of
ui_out_table with an enum.  It expresses more explicitly the
intent of the field (check that state == TABLE_STATE_HEADERS conveys
more what we want to do than checking for !body_flag).

New in v2:

  - Remove unnecessary ui_out_table_state::.

gdb/ChangeLog:

	* ui-out.c (enum ui_out_table_state): New enum.
	(struct ui_out_table) <body_flag>: Remove field.
	<state>: New field.
	(ui_out_table_begin): Replace usages of body_flag with state.
	(ui_out_table_body): Likewise.
	(ui_out_table_end): Likewise.
	(ui_out_table_header): Likewise.
	(ui_out_begin): Likewise.
	(verify_field): Likewise.
	(ui_out_new): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Class-ify ui_out_table
@ 2016-12-02  5:34 sergiodj+buildbot
  2016-12-14 12:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  5:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36d18bc526b055be896d8dc319cb3ade42238534 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 36d18bc526b055be896d8dc319cb3ade42238534

Class-ify ui_out_table

This patch makes a class out of the ui_out_table structure, the
structure responsible for managing the generation of an UI table.

To simplify the ui_out_table object, I changed it so that it can only be
used for generating a single object.  Instead of clearing the header
list when starting a new table, we an ui_out_table when starting a
table and delete it when we're done.  Therefore, the checks:

  if (uiout->table->flag)
  if (!uiout->table->flag)

are respectively replaced with

  if (uiout->table != nullptr)
  if (uiout->table == nullptr)

Note: I removed the check at the beginning of ui_out_begin, because
there is an equivalent check at the beginning of verify_field.

New in v2:

  - use "enum class" for ui_out_table::state and update references.

gdb/ChangeLog:

	* ui-out.c (enum ui_out_table_state): Move to class
	ui_out_table as ui_out_table::state.
	(struct ui_out_table): Change to ...
	(class ui_out_table): ... this.
	<flag>: Remove.
	<entry_level>: Rename to ...
	<m_entry_level>: ... this.
	<columns>: Rename to ...
	<m_nr_cols>: ... this.
	<id>: Rename to ...
	<m_id>: ... this.
	<headers>: Rename to ...
	<m_headers>: ... this.
	<headers_iterator>: Rename to ...
	<m_headers_iterator>: ... this.
	<start_body, append_header, start_row, get_next_header,
	query_field, current_state, entry_level>: New methods.
	(struct ui_out) <table>: Change type to unique_ptr to
	ui_out_table.
	(append_header_to_list, get_next_header, clear_header_list,
	clear_table): Remove.
	(ui_out_table_begin): Instantiate ui_out_table object.  Update
	table check.
	(ui_out_table_body): Update table check, replace code with call
	to ui_out_table::start_body.
	(ui_out_table_end): Update table check, replace manual cleanup
	with assignment of uiout->table unique_ptr to nullptr.
	(ui_out_table_header): Update table check, replace call to
	append_header_to_list with call to append_header method.
	(ui_out_begin): Remove one table state check, update another.
	Replace code with call to start_row method.
	(verify_field): Update table checks.
	(ui_out_query_field): Update table check, replace code with call
	to query_field method.
	(ui_out_new): Remove table initialization code.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't handle timeout inside gdb_test_multiple
@ 2016-12-02  6:01 sergiodj+buildbot
  2016-12-14 17:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  6:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 018572b88885ae67d22612937fa1e4fd98d5f5ad ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 018572b88885ae67d22612937fa1e4fd98d5f5ad

Don't handle timeout inside gdb_test_multiple

This fixes a few cases where the testcase is explicitly handling timeouts
inside gdb_test_multiple when it is not necessary.

It also converts two gdb_test_multiple calls to gdb_test_no_output calls
(also removing the timeout handling).

gdb/testsuite/ChangeLog:

2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.base/maint.exp: Remove timeout handling for gdb_test_multiple.
	* gdb.cp/gdb2495.exp: Likewise and convert gdb_test_multiple into
	gdb_test_no_output for a couple of cases.
	* gdb.cp/ovldbreak.exp: Remove timeout handling for gdb_test_multiple.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add unit test to aarch64 prologue analyzer
@ 2016-12-02 10:11 sergiodj+buildbot
  2016-12-14 21:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 10:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d9a9006139d1ceea787cdda871dff8943e493f0 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 4d9a9006139d1ceea787cdda871dff8943e493f0

Add unit test to aarch64 prologue analyzer

We don't have an effective way to test prologue analyzer which is
highly dependent on instruction patterns in prologue generated by
compiler.  GDB prologue analyzer may not handle the new sequences
generated by new compiler, or may still handle some sequences that
generated by very old compilers which are no longer used.  The
former is a functionality issue, while the latter is a maintenance
issue.

The input and output of prologue analyzer is quite clear, so it
fits for unit test.  The input is series of instructions, and the
output are 1) where prologue end, 2) where registers are saved.
In aarch64, they are represented in 'struct aarch64_prologue_cache'.

This patch refactors aarch64_analyze_prologue so it can read
instructions from either real target or test harness.  In unit
test aarch64_analyze_prologue_test, aarch64_analyze_prologue gets
instructions we prepared in the test, as the input of prologue
analyzer.  Then, we checked various fields in
'struct aarch64_prologue_cache'.

gdb:

2016-12-02  Yao Qi  <yao.qi@linaro.org>
	    Pedro Alves  <palves@redhat.com>

	* aarch64-tdep.c: Include "selftest.h".
	(abstract_instruction_reader): New class.
	(instruction_reader): New class.
	(aarch64_analyze_prologue): Add new parameter reader.  Call
	reader.read instead of read_memory_unsigned_integer.
	[GDB_SELF_TEST] (instruction_reader_test): New class.
	(aarch64_analyze_prologue_test): New function.
	(_initialize_aarch64_tdep) [GDB_SELF_TEST]: Register
	selftests::aarch64_analyze_prologue_test.
	* trad-frame.c (trad_frame_cache_zalloc):
	(trad_frame_alloc_saved_regs): Add a new function.
	* trad-frame.h (trad_frame_alloc_saved_regs): Declare.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Recognize STR instruction in prologue
@ 2016-12-02 10:50 sergiodj+buildbot
  2016-12-14 22:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 10:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 432ec0814b01a93b88eddf13092ea6abef34652d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 432ec0814b01a93b88eddf13092ea6abef34652d

[AArch64] Recognize STR instruction in prologue

This patch teaches GDB AArch64 backend to recognize STR instructions
in prologue, like 'str x19, [sp, #-48]!' or 'str w0, [sp, #44]'.
The unit test is added too.

gdb:

2016-12-02  Yao Qi  <yao.qi@linaro.org>
	    Pedro Alves  <palves@redhat.com>

	* aarch64-tdep.c (aarch64_analyze_prologue): Recognize STR
	instruction.
	(aarch64_analyze_prologue_test): More tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for Fushia OS.
@ 2016-12-02 11:30 sergiodj+buildbot
  2016-12-15  1:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 11:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5451cd45325d12b2cc3d10ffe67f09b0e26b967 ***

Author: Josh Conner <joshconner@google.com>
Branch: master
Commit: d5451cd45325d12b2cc3d10ffe67f09b0e26b967

Add support for Fushia OS.

        * configure.ac: Add fuchsia to targets that use ELF.
        * configure: Regenerated.

bfd     * configure.tgt: Add support for fuchsia (OS).

gas     * configure.tgt: Add support for fuchsia (OS).

ld      * Makefile.am: Add dependency information for earmelf_fuchsia.c.
        * Makefile.in: Regenerate.
        * configure.tgt: Add support for aarch64-*-fuchsia, arm*-*-fuchsia*, and
        x86_64-*-fuchsia* targets.
        * emulparams/armelf_fuchsia.sh: New file.
        * emulparams/armelfb_fuchsia.sh: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Always pass a valid section header offset to elf_parse_notes
@ 2016-12-02 12:02 sergiodj+buildbot
  2016-12-15  4:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 08698b7b46c9c932530dcbcd7e851d27a7d2c503 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 08698b7b46c9c932530dcbcd7e851d27a7d2c503

Always pass a valid section header offset to elf_parse_notes

_bfd_elf_make_section_from_shdr calls elf_parse_notes with an offset
of -1.  This argument is used to calculate Elf_Internal_Note.descpos,
which ends up set to a positive but meaningless value.  This commit
updates _bfd_elf_make_section_from_shdr to pass the correct offset to
elf_parse_notes, making Elf_Internal_Note.descpos correct in all cases.

bfd/ChangeLog:

	* elf.c (_bfd_elf_make_section_from_shdr): Pass offset to
	elf_parse_notes.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove mi_out_data::suppress_output
@ 2016-12-02 15:26 sergiodj+buildbot
  2016-12-15  8:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 15:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 233c8c27eb81b0a3ab5182dcb59c7306ba9bd3f3 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 233c8c27eb81b0a3ab5182dcb59c7306ba9bd3f3

Remove mi_out_data::suppress_output

The suppress_output field of the mi_ui_out_data structure is never actually
set to 1/true.  We can therefore remove it, and remove all the

  if (suppress_output)

checks.

gdb/ChangeLog:

	* mi/mi-out.c (mi_ui_out_data) <suppress_output>: Remove.
	(mi_table_body): Remove suppress_output check.
	(mi_table_end): Likewise.
	(mi_table_header): Likewise.
	(mi_begin): Likewise.
	(mi_end): Likewise.
	(mi_field_int): Likewise.
	(mi_field_string): Likewise.
	(mi_field_fmt): Likewise.
	(mi_out_data_ctor): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Rename some trace functions
@ 2016-12-02 16:03 sergiodj+buildbot
  2016-12-15 12:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e5a873b7071d74320d4e0cbbc2f358dcf2322557 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: e5a873b7071d74320d4e0cbbc2f358dcf2322557

Rename some trace functions

This patch renames a few trace-related functions, so that they adhere to
the de facto standard of naming command entry point functions
<command>_command.  I like the ease of looking up a command entry point
if they all follow that rule.

An enum label "tstop_command" conflicts with a new function name, so I
renamed this one trace_stop_command.

In v2:

- Rename functions of the trace_find family, as well as
  trace_dump_command.

gdb/ChangeLog:

	* tracefile-tfile.c (tfile_write_status): Adjust to renames.
	* tracefile.c (trace_save_command): Rename to...
	(tsave_command): ...this.
	(_initialize_tracefile): Adjust to renames.
	* tracepoint.c (trace_actions_command): Rename to...
	(actions_command): ...this.
	(trace_start_command): Rename to...
	(tstart_command): ...this, and adjust to renames..
	(trace_stop_command): Rename to...
	(tstop_command): ...this.
	(trace_status_command): Rename to...
	(tstatus_command): ...this, and adjust to renames.
	(trace_find_command): Rename to...
	(tfind_command): ...this.
	(trace_find_pc_command): Rename to...
	(tfind_pc_command): ...this.
	(trace_find_tracepoint_command): Rename to...
	(tfind_tracepoint_command): ...this.
	(trace_find_line_command): Rename to...
	(tfind_line_command): ...this.
	(trace_find_range_command): Rename to...
	(tfind_range_command): ...this.
	(trace_find_outside_command): Rename to...
	(tfind_outside_command): ...this.
	(trace_dump_command): Rename to...
	(tdump_command): ...this.
	(tfind_1): Adjust to renames.
	(trace_find_end_command): Rename to...
	(tfind_end_command): ...this, and adjust to renames..
	(trace_status_mi): Adjust to renames.
	(parse_trace_status): Adjust to renames.
	(_initialize_tracepoint): Adjust to renames.
	* tracepoint.h (enum trace_stop_reason) <tstop_command>: Rename
	to...
	<trace_stop_command>: ...this.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR symtab/16264 - support DW_AT_main_subprogram
@ 2016-12-02 16:48 sergiodj+buildbot
  2016-12-15 13:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 16:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c1b455e294c6debb4efedc7f1346f3c43249f15 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 0c1b455e294c6debb4efedc7f1346f3c43249f15

PR symtab/16264 - support DW_AT_main_subprogram

This patch adds support for DW_AT_main_subprogram.
This is PR symtab/16264.

DW_AT_main_subprogram is used to mark a program's entry point.  GCC
can emit this, and I hope to change the Rust compiler to emit it as
well.

GDB already supports an older, pre-DWARF 4 convention adopted by
FORTRAN compilers, namely to emit DW_AT_calling_convention for the
"main" function.  However, I think this support in GDB had a small
bug, in that it seems to rely on the DW_AT_name being read before
DW_AT_calling_convention.  This patch fixes this as well.

Built and regtested on x86-64 Fedora 24 and the buildbot.  New test
case included.

2016-12-02  Tom Tromey  <tom@tromey.com>

	PR symtab/16264:
	* dwarf2read.c (struct partial_die_info) <main_subprogram>: New
	member.
	(add_partial_symbol): Call set_objfile_main_name.
	(read_partial_die): Handle DW_AT_main_subprogram.
	<DW_AT_calling_convention>: don't call set_objfile_main_name, but
	set main_subprogram flag.

2016-12-02  Tom Tromey  <tom@tromey.com>

	* gdb.dwarf2/main-subprogram.c: New file.
	* gdb.dwarf2/main-subprogram.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix seg-fault in the linker when examining a corrupt binary.
@ 2016-12-02 17:12 sergiodj+buildbot
  2016-12-15 17:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 17:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 531336e3a0b79ed60cfc36ad2d6579b6a71175da ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 531336e3a0b79ed60cfc36ad2d6579b6a71175da

Fix seg-fault in the linker when examining a corrupt binary.

	PR ld/20909
	* aoutx.h (aout_link_add_symbols): Fix off-by-one error in check
	for an illegal string offset.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Revert change to gdb.cp/ovldbreak.exp
@ 2016-12-02 18:11 sergiodj+buildbot
  2016-12-15 20:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 18:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 008459ea88ad4fdcb7da37dad7f68888ef6ecc47 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 008459ea88ad4fdcb7da37dad7f68888ef6ecc47

Revert change to gdb.cp/ovldbreak.exp

This reverts the timeout handling (removed by
018572b88885ae67d22612937fa1e4fd98d5f5ad) for gdb.cp/ovldbreak.exp until we
decide what to do about this particular function.

gdb/testsuite/ChangeLog:

2016-12-02  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.base/ovldbreak.exp (take_gdb_out_of_choice_menu): Restore
	timeout handling.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix seg-fault in linker when passed a corrupt binary input file.
@ 2016-12-02 18:56 sergiodj+buildbot
  2016-12-15 23:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 18:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d7f399a8de4c55eb841db6493597a587fac002de ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: d7f399a8de4c55eb841db6493597a587fac002de

Fix seg-fault in linker when passed a corrupt binary input file.

	PR lf/20908
	* elflink.c (bfd_elf_final_link): Check for ELF flavour binaries
	when following indirect links.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR 20559 - "eval" command and $arg0...$arg9/$argc substitution
@ 2016-12-02 19:55 sergiodj+buildbot
  2016-12-16  2:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 19:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01770bbde902e075e524b518ac6c1087a4cc1cfb ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 01770bbde902e075e524b518ac6c1087a4cc1cfb

Fix PR 20559 - "eval" command and $arg0...$arg9/$argc substitution

It'd be handy to be able to iterate over command arguments in
user-defined commands, in order to support optional arguments
($arg0..$argN).

I thought I could make it work with "eval", but alas, it doesn't work
currently.  E.g., with:

 define test
   set $i = 0
   while $i < $argc
     eval "print $arg%d", $i
     set $i = $i + 1
   end
 end

we get:

 (gdb) test 1
 $1 = void
 (gdb) test 1 2 3
 $2 = void
 $3 = void
 $4 = void
 (gdb)

The problem is that "eval" doesn't do user-defined command arguments
substitution after expanding its own argument.  This patch fixes that,
which makes the example above work:

 (gdb) test 1
 $1 = 1
 (gdb) test 1 2 3
 $2 = 1
 $3 = 2
 $4 = 3
 (gdb)

New test included, similar the above, but also exercises expanding
$argc.

I think this is likely to simplify many scripts out there, so I'm
adding an example to the manual and mentioning it in NEWS as well.

gdb/ChangeLog:
2016-12-02  Pedro Alves  <palves@redhat.com>

	PR cli/20559
	* NEWS: Mention "eval" expands user-defined command arguments.
	* cli/cli-script.c (execute_control_command): Adjust to rename.
	(insert_args): Rename to ...
	(insert_user_defined_cmd_args): ... this, and make extern.
	* cli/cli-script.h (insert_user_defined_cmd_args): New
	declaration.
	* printcmd.c: Include "cli/cli-script.h".
	(eval_command): Call insert_user_defined_cmd_args.

gdb/doc/ChangeLog:
2016-12-02  Pedro Alves  <palves@redhat.com>

	PR cli/20559
	* gdb.texinfo (Define): Add example of using "eval" to process a
	variable number of arguments.
	(Output) <eval>: Add anchor.

gdb/testsuite/ChangeLog:
2016-12-02  Pedro Alves  <palves@redhat.com>

	PR cli/20559
	* gdb.base/commands.exp (user_defined_command_args_eval): New
	procedure.
	(top level): Call it.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Test user-defined gdb commands and arguments stack
@ 2016-12-02 20:34 sergiodj+buildbot
  2016-12-16  3:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 20:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec835369f121c11d6e9484ed8c6c11097ad545c5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ec835369f121c11d6e9484ed8c6c11097ad545c5

Test user-defined gdb commands and arguments stack

We're missing a test that makes sure that arguments to user-defined
commands are handled correctly when a user-defined command calls
another user-defined command / recurses.

The following patch changes that code, so add such a test first so we
can be confident won't be breaking this use case.

gdb/testsuite/ChangeLog:
2016-12-02  Pedro Alves  <palves@redhat.com>

	* gdb.base/commands.exp (user_defined_command_args_stack_test):
	New procedure.
	(top level): Call it.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Support an "unlimited" number of user-defined arguments
@ 2016-12-02 21:13 sergiodj+buildbot
  2016-12-16  7:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 21:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df3ee9ca894f7e831713c332aa7820a6463c2435 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: df3ee9ca894f7e831713c332aa7820a6463c2435

Support an "unlimited" number of user-defined arguments

New in v2:

  - A few adjustments / simplifications were possible now that we
    require C++11:

    . Use std::unique_ptr to make the user_args_stack std::vector own
      its elements:

       static std::vector<std::unique_ptr<user_args>> user_args_stack;

    . use vector::emplace_back to construct elements directly in the
      corresponding vectors.

    . use std::to_string instead of adding a gdb::to_string
      replacement.

  - Now includes a test.

Docs/NEWS are unchanged from v1 and have already been approved.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I recently wrote a user-defined command that could benefit from
supporting an unlimited number of arguments:

 http://palves.net/list-active-signal-handlers-with-gdb/

E.g., 'info signal-dispositions 1 2 3 4 5 6 7 8 9 10 11'

However, we currently only support up to 10 arguments passed to
user-defined commands ($arg0..$arg9).

I can't find a good reason for that, other than "old code with hard
coded limits".  This patch removes that limit and modernizes the code
along the way:

  - Makes the user_args struct a real C++ class that uses std::vector
    for storage.

  - Removes the "next" pointer from within user_args and uses a
    std::vector to maintain a stack instead.

  - Adds a new RAII-based scoped_user_args_level class to help
    push/pop user args in the stack instead of using a cleanup.

gdb/ChangeLog:
2016-12-02  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention that user commands now accept an unlimited number
	of arguments.
	* cli/cli-script.c: Include <vector>.
	(struct string_view): New type.
	(MAXUSERARGS): Delete.
	(struct user_args): Now a C++ class.
	(user_args_stack): New.
	(struct scoped_user_args_level): New type.
	(execute_user_command): Use scoped_user_args_level.
	(arg_cleanup): Delete.
	(setup_user_args): Deleted, and refactored as ...
	(user_args::user_args): ... this new constructor.  Limit of number
	of arguments removed.
	(insert_user_defined_cmd_args): Defer to user_args_stack.
	(user_args::insert_args): New, bits based on old
	insert_user_defined_cmd_args with limit of number of arguments
	eliminated.

gdb/doc/ChangeLog:
2016-12-02  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (User-defined Commands): Limit on number of
	arguments passed to user-defined commands removed; update.

gdb/testsuite/ChangeLog:
2016-12-02  Pedro Alves  <palves@redhat.com>

	* gdb.base/commands.exp (user_defined_command_manyargs_test): New
	procedure.
	(top level): Call it.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove unneeded pattern matching in gdb.base/maint.exp
@ 2016-12-02 21:50 sergiodj+buildbot
  2016-12-16 11:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 107c2d628b924de1854d6d254d60e97e1887ce4a ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 107c2d628b924de1854d6d254d60e97e1887ce4a

Remove unneeded pattern matching in gdb.base/maint.exp

This gets rid of more useless pattern matching cases in gdb.base/maint.exp.

gdb/testsuite/ChangeLog:

2016-12-02  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.base/maint.exp: Use gdb_test instead of gdb_test_multiple when
	possible.
	Remove useless pattern-matching code.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Introduce enum_flag type for ui_out flags
@ 2016-12-02 22:35 sergiodj+buildbot
  2016-12-16 12:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 22:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bef721e278d9ba3178e679eda38ac86ef2dc0d5d ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: bef721e278d9ba3178e679eda38ac86ef2dc0d5d

Introduce enum_flag type for ui_out flags

This patch changes the ui_out flags to be an enum flag.

gdb/ChangeLog:

	* ui-out.h: Include "common/enum-flags.h".
	(enum ui_flags): Rename to ...
	(enum ui_out_flag): ... this.
	(ui_out_flags): Define enum flag type.
	(ui_out_test_flags): Change type of parameter to ui_out_flags.
	(ui_out_new): Likewise.
	* ui-out.c (ui_out_test_flags): Likewise.
	(ui_out_new): Likewise.
	* cli-out.c (cli_out_new): Update variable type.
	* mi/mi-out.c (mi_out_new): Likewise.
	* tui/tui-out.c (tui_out_new): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] ppc64_elf_copy_indirect_symbol versioned_hidden fix
@ 2016-12-03 11:13 sergiodj+buildbot
  2016-12-16 16:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-03 11:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 474436e67c72d2426e79e600d725812514db0dbe ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 474436e67c72d2426e79e600d725812514db0dbe

ppc64_elf_copy_indirect_symbol versioned_hidden fix

As per _bfd_elf_link_hash_copy_indirect.

	* elf64-ppc.c (ppc64_elf_copy_indirect_symbol): Don't copy dynamic
	flags when direct symbol is versioned_hidden.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Indirect and warning symbols
@ 2016-12-03 11:55 sergiodj+buildbot
  2016-12-16 18:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-03 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8400d40d954ec3b4a3fe9200645a1b6e90ba46f4 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 8400d40d954ec3b4a3fe9200645a1b6e90ba46f4

Indirect and warning symbols

It's possible but unlikely that an indirect symbol points at a warning
symbol.

	* elf64-ppc.c (add_symbol_adjust): Correct order of tests for
	warning and indirect symbols.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PowerPC64 add_symbol_adjust
@ 2016-12-03 12:21 sergiodj+buildbot
  2016-12-16 22:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-03 12:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35dc6e06960790cd60b890c14e45f82f110b898f ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 35dc6e06960790cd60b890c14e45f82f110b898f

PowerPC64 add_symbol_adjust

	* elf64-ppc.c (add_symbol_adjust): Delete dead code.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Tidy ppc64_elf_hide_symbol
@ 2016-12-03 13:02 sergiodj+buildbot
  2016-12-17  3:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-03 13:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8ac28419be22fe0cc72f6eaaba1ab029610fc71 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: b8ac28419be22fe0cc72f6eaaba1ab029610fc71

Tidy ppc64_elf_hide_symbol

	* elf64-ppc.c (ppc64_elf_hide_symbol): Access hash table as
	elf_link_hash_table rather than ppc_link_hash_table.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PowerPC64 dot-symbol compatibility bugfixes
@ 2016-12-03 13:35 sergiodj+buildbot
  2016-12-17  6:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-03 13:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8c5b4e5228ec94923fbdfb0008926b0b2a3f51c2 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 8c5b4e5228ec94923fbdfb0008926b0b2a3f51c2

PowerPC64 dot-symbol compatibility bugfixes

Lots of fixes for the compatibility code that handles linking of
-mcall-aixdesc code (or that generated by 12 year old gcc) with
current ELFv1 ABI code.

1) A reference to a dot-symbol in an object file wasn't satisfied by a
   function descriptor in later object files.
2) The as-needed code had bit-rotted;  Shared libs now need a strong
   reference to be counted as needed.
3) --gc-sections involving dot-symbols was broken, needing
   func_desc_adjust to be run early and lots of other fixes.

bfd/
	* elf64-ppc.c (struct ppc_link_hash_entry): Delete "was_undefined".
	(struct ppc_link_hash_table): Delete "twiddled_syms".  Add
	"need_func_desc_adj".
	(lookup_fdh): Link direct fdh sym via oh field and set flags.
	(make_fdh): Make strong and weak undefined function descriptor
	symbols.
	(ppc64_elf_merge_symbol): New function.
	(elf_backend_merge_symbol): Define.
	(ppc64_elf_archive_symbol_lookup): Don't test undefweak for fake
	function descriptors.
	(add_symbol_adjust): Don't twiddle symbols to undefweak.
	Propagate more ref flags to function descriptor symbol.  Make
	some function descriptor symbols dynamic.
	(ppc64_elf_before_check_relocs): Only run add_symbol_adjust for
	ELFv1.  Set need_func_desc_adj.  Don't fix undefs list.
	(ppc64_elf_check_relocs): Set non_ir_ref for descriptors.
	Don't call lookup_fdh here.
	(ppc64_elf_gc_sections): New function.
	(bfd_elf64_bfd_gc_sections): Define.
	(ppc64_elf_gc_mark_hook): Mark descriptor.
	(func_desc_adjust): Don't make fake function descriptor syms strong
	here.  Exit earlier on non-dotsyms.  Take note of elf.dynamic
	flag when deciding whether a dynamic function descriptor might
	be needed.  Transfer elf.dynamic and set elf.needs_plt.  Move
	plt regardless of visibility.  Make descriptor dynamic if
	entry sym is dynamic, not for other cases.
	(ppc64_elf_func_desc_adjust): Don't run func_desc_adjust if
	already done.
	(ppc64_elf_edit_opd): Use oh field rather than lookup_fdh.
	(ppc64_elf_size_stubs): Likewise.
	(ppc_build_one_stub): Don't clear was_undefined.  Only set sym
	undefweak if stub symbol is defined.
	(undo_symbol_twiddle, ppc64_elf_restore_symbols): Delete.
	* elf64-ppc.h (ppc64_elf_restore_symbols): Don't declare.
ld/
	* emultempl/ppc64elf.em (gld${EMULATION_NAME}_finish): Don't call
	ppc64_elf_restore_symbols.
	* testsuite/ld-powerpc/dotsym1.d: New.
	* testsuite/ld-powerpc/dotsym2.d: New.
	* testsuite/ld-powerpc/dotsym3.d: New.
	* testsuite/ld-powerpc/dotsym4.d: New.
	* testsuite/ld-powerpc/dotsymref.s: New.
	* testsuite/ld-powerpc/nodotsym.s: New.
	* testsuite/ld-powerpc/powerpc.exp: Run new tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix bugs with tbnz/tbz instructions.
@ 2016-12-04  2:02 sergiodj+buildbot
  2016-12-17 14:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-04  2:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 668650d58d61d9d170f3e5b5c1657ed1c3e2b34b ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: 668650d58d61d9d170f3e5b5c1657ed1c3e2b34b

Fix bugs with tbnz/tbz instructions.

sim/aarch64
	* simulator.c (tbnz, tbz): Cast 1 to uint64_t before shifting.
	(dexTestBranchImmediate): Shift high bit of pos by 5 not 4.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <@gdb-build>]
* [binutils-gdb] Correct assembler mnemonic for RISC-V aqrl AMOs
@ 2016-12-20  2:06 sergiodj+buildbot
  2016-12-23 21:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-20  2:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e67a37820a2838cdbd50f3f697ddc929443ceaa ***

Author: Andrew Waterman <andrew@sifive.com>
Branch: master
Commit: 3e67a37820a2838cdbd50f3f697ddc929443ceaa

Correct assembler mnemonic for RISC-V aqrl AMOs

sc is a misnomer, because they aren't inherently sc.

	* riscv-opc.c (riscv_opcodes): Rename the "*.sc" instructions to
	"*.aqrl".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS16/opcodes: Correct 64-bit macros' ISA membership
@ 2016-12-20 14:09 sergiodj+buildbot
  2016-12-24  4:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-20 14:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ebce1a0a5911e71aa2d00932ffb2126ff1f3633 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 4ebce1a0a5911e71aa2d00932ffb2126ff1f3633

MIPS16/opcodes: Correct 64-bit macros' ISA membership

Limit the DDIV, DDIVU, DREM, DREMU and DSUBU macros to the MIPS III
rather than MIPS I ISA.  These macros expand to machine code sequences
including 64-bit instructions which require a 64-bit ISA.  Entries for
those instructions are already correctly marked, however the marking is
ignored if entries are used in the process of macro expansion rather
than directly, making it possible to indirectly produce 64-bit machine
code even when output requested has been limited to a 32-bit ISA.

	opcodes/
	* mips16-opc.c (mips16_opcodes): Set membership to I3 rather
	than I1 for the "ddiv", "ddivu", "drem", "dremu" and "dsubu"
	INSN_MACRO entries.

	gas/
	* testsuite/gas/mips/mips16-macro.l: New list test.
	* testsuite/gas/mips/mips.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS16/opcodes: Respect ISA and ASE in disassembly
@ 2016-12-20 15:08 sergiodj+buildbot
  2016-12-24 13:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-20 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 11dd08e9a0a2b7115aac32d9599f1bdb0ad12ea6 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 11dd08e9a0a2b7115aac32d9599f1bdb0ad12ea6

MIPS16/opcodes: Respect ISA and ASE in disassembly

Limit MIPS16 instruction disassembly according to the ISA level and ASE
set selected, as with the regular MIPS and microMIPS instruction sets.
Retain the property of `objdump -m mips:16' disassembling all MIPS16
instructions however, regardless of any ISA level recorded in the binary
examined.

To validate the disassembler use the GAS test suite for its convenience
of running tests across multiple ISAs, even though placing the tests in
the binutils test suite would be more appropriate.  Adjust the single
binutils test which depends on 64-bit instruction disassembly to have
the ISA level required actually recorded in the binary examined.

	opcodes/
	* mips-dis.c (mips_arch_choices): Use ISA_MIPS64 rather than
	ISA_MIPS3 as the `isa' selection in the `bfd_mach_mips16' entry.
	(print_insn_mips16): Check opcode entries for validity against
	the ISA level and ASE set selected.

	binutils/
	* testsuite/binutils-all/mips/mips16-undecoded.s: Use `.module'
	rather than `.set' to set the ISA level.

	gas/
	* testsuite/gas/mips/mips16-sub.d: New test.
	* testsuite/gas/mips/mips16-32@mips16-sub.d: New test.
	* testsuite/gas/mips/mips16e-32@mips16-sub.d: New test.
	* testsuite/gas/mips/mips16e-sub.d: New test.
	* testsuite/gas/mips/mips16-32@mips16e-sub.d: New test.
	* testsuite/gas/mips/mips16-64@mips16e-sub.d: New test.
	* testsuite/gas/mips/mips16e-64-sub.d: New test.
	* testsuite/gas/mips/mips16-32@mips16e-64-sub.d: New test.
	* testsuite/gas/mips/mips16-64@mips16e-64-sub.d: New test.
	* testsuite/gas/mips/mips16e-32@mips16e-64-sub.d: New test.
	* testsuite/gas/mips/mips16-sub.s: New test source.
	* testsuite/gas/mips/mips16e-sub.s: New test source.
	* testsuite/gas/mips/mips16e-64-sub.s: New test source.
	* testsuite/gas/mips/mips.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Avoid creating symbol table entries for registers
@ 2016-12-21 14:46 sergiodj+buildbot
  2016-12-25 17:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-21 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 58a6d3c9d8d4d4be8f1dfc1a49fed264dceddaba ***

Author: Andrew Waterman <andrew@sifive.com>
Branch: master
Commit: 58a6d3c9d8d4d4be8f1dfc1a49fed264dceddaba

Avoid creating symbol table entries for registers

Instructions like "jal t0, foo" were erroneously creating symbol table
entries for t0 as well as foo, which causes linking problems.  Fix by
reordering instruction alternatives so that t0 is first attempted to
be parsed as a register, rather than as a symbol.

	* riscv-opc.c (riscv_opcodes): Reorder jal and call entries.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't make_bfd_vms_lib archive functions NULL
@ 2016-12-21 15:21 sergiodj+buildbot
  2016-12-25 20:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-21 15:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0d19df99dfe1c63842206d15ae41dfd33d25bf0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: f0d19df99dfe1c63842206d15ae41dfd33d25bf0

Don't make_bfd_vms_lib archive functions NULL

Contrary to the comment, they can in fact be called.

	* libbfd-in.h (_bfd_vms_lib_slurp_armap): Use _bfd_noarchive function.
	(_bfd_vms_lib_slurp_extended_name_table: Likewise.
	(_bfd_vms_lib_construct_extended_name_table: Likewise.
	(_bfd_vms_lib_truncate_arname: Likewise.
	(_bfd_vms_lib_write_armap: Likewise.
	(_bfd_vms_lib_read_ar_hdr: Likewise.
	(_bfd_vms_lib_write_ar_hdr: Likewise.
	* libbfd.h: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Updated email address.
@ 2016-12-23 12:50 sergiodj+buildbot
  2016-12-27  6:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 12:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6096dda15babc5307b1a0e9624d4e0028fd429e1 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 6096dda15babc5307b1a0e9624d4e0028fd429e1

Updated email address.

2016-12-23  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* MAINTAINERS (Write After Approval): Updated email address.

Change-Id: I46b81392c2bd4b04e8e2aea2bb4bef2d0b509d24


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix more cases of improper test names
@ 2016-12-23 20:03 sergiodj+buildbot
  2016-12-28  3:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 20:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b362f04b2a56d446b024027963be52d61f939cb ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 5b362f04b2a56d446b024027963be52d61f939cb

Fix more cases of improper test names

I noticed more occurrences of improper test names. The rather mechanical,
tedious and large patch below addresses, hopefully, most of the leftover cases.

As usual, another pair of eyes is welcome to check if missed something or did
an invalid substitution.

This patch also fixes the prepare_for_testing calls to pass proper test names.

gdb/testsuite/ChangeLog:

2016-12-23  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names for the following files:

	* gdb.ada/exec_changed.exp
	* gdb.ada/info_types.exp
	* gdb.arch/aarch64-atomic-inst.exp
	* gdb.arch/aarch64-fp.exp
	* gdb.arch/altivec-abi.exp
	* gdb.arch/altivec-regs.exp
	* gdb.arch/amd64-byte.exp
	* gdb.arch/amd64-disp-step.exp
	* gdb.arch/amd64-dword.exp
	* gdb.arch/amd64-entry-value-inline.exp
	* gdb.arch/amd64-entry-value-param.exp
	* gdb.arch/amd64-entry-value-paramref.exp
	* gdb.arch/amd64-entry-value.exp
	* gdb.arch/amd64-i386-address.exp
	* gdb.arch/amd64-invalid-stack-middle.exp
	* gdb.arch/amd64-invalid-stack-top.exp
	* gdb.arch/amd64-optimout-repeat.exp
	* gdb.arch/amd64-prologue-skip.exp
	* gdb.arch/amd64-prologue-xmm.exp
	* gdb.arch/amd64-stap-special-operands.exp
	* gdb.arch/amd64-stap-wrong-subexp.exp
	* gdb.arch/amd64-tailcall-cxx.exp
	* gdb.arch/amd64-tailcall-noret.exp
	* gdb.arch/amd64-tailcall-ret.exp
	* gdb.arch/amd64-tailcall-self.exp
	* gdb.arch/amd64-word.exp
	* gdb.arch/arm-bl-branch-dest.exp
	* gdb.arch/arm-disp-step.exp
	* gdb.arch/arm-neon.exp
	* gdb.arch/arm-single-step-kernel-helper.exp
	* gdb.arch/avr-flash-qualifier.exp
	* gdb.arch/disp-step-insn-reloc.exp
	* gdb.arch/e500-abi.exp
	* gdb.arch/e500-regs.exp
	* gdb.arch/ftrace-insn-reloc.exp
	* gdb.arch/i386-avx512.exp
	* gdb.arch/i386-bp_permanent.exp
	* gdb.arch/i386-byte.exp
	* gdb.arch/i386-cfi-notcurrent.exp
	* gdb.arch/i386-disp-step.exp
	* gdb.arch/i386-dr3-watch.exp
	* gdb.arch/i386-float.exp
	* gdb.arch/i386-gnu-cfi.exp
	* gdb.arch/i386-mpx-map.exp
	* gdb.arch/i386-mpx-sigsegv.exp
	* gdb.arch/i386-mpx-simple_segv.exp
	* gdb.arch/i386-mpx.exp
	* gdb.arch/i386-permbkpt.exp
	* gdb.arch/i386-prologue.exp
	* gdb.arch/i386-signal.exp
	* gdb.arch/i386-size-overlap.exp
	* gdb.arch/i386-unwind.exp
	* gdb.arch/i386-word.exp
	* gdb.arch/mips-fcr.exp
	* gdb.arch/powerpc-d128-regs.exp
	* gdb.arch/powerpc-stackless.exp
	* gdb.arch/ppc64-atomic-inst.exp
	* gdb.arch/s390-stackless.exp
	* gdb.arch/s390-tdbregs.exp
	* gdb.arch/s390-vregs.exp
	* gdb.arch/sparc-sysstep.exp
	* gdb.arch/thumb-bx-pc.exp
	* gdb.arch/thumb-singlestep.exp
	* gdb.arch/thumb2-it.exp
	* gdb.arch/vsx-regs.exp
	* gdb.asm/asm-source.exp
	* gdb.base/a2-run.exp
	* gdb.base/advance.exp
	* gdb.base/all-bin.exp
	* gdb.base/anon.exp
	* gdb.base/args.exp
	* gdb.base/arithmet.exp
	* gdb.base/async-shell.exp
	* gdb.base/async.exp
	* gdb.base/attach-pie-noexec.exp
	* gdb.base/attach-twice.exp
	* gdb.base/auto-load.exp
	* gdb.base/bang.exp
	* gdb.base/bitfields.exp
	* gdb.base/break-always.exp
	* gdb.base/break-caller-line.exp
	* gdb.base/break-entry.exp
	* gdb.base/break-inline.exp
	* gdb.base/break-on-linker-gcd-function.exp
	* gdb.base/break-probes.exp
	* gdb.base/break.exp
	* gdb.base/breakpoint-shadow.exp
	* gdb.base/call-ar-st.exp
	* gdb.base/call-sc.exp
	* gdb.base/call-signal-resume.exp
	* gdb.base/call-strs.exp
	* gdb.base/callfuncs.exp
	* gdb.base/catch-fork-static.exp
	* gdb.base/catch-gdb-caused-signals.exp
	* gdb.base/catch-load.exp
	* gdb.base/catch-signal-fork.exp
	* gdb.base/catch-signal.exp
	* gdb.base/catch-syscall.exp
	* gdb.base/charset.exp
	* gdb.base/checkpoint.exp
	* gdb.base/chng-syms.exp
	* gdb.base/code-expr.exp
	* gdb.base/code_elim.exp
	* gdb.base/commands.exp
	* gdb.base/completion.exp
	* gdb.base/complex.exp
	* gdb.base/cond-expr.exp
	* gdb.base/condbreak.exp
	* gdb.base/consecutive.exp
	* gdb.base/continue-all-already-running.exp
	* gdb.base/coredump-filter.exp
	* gdb.base/corefile.exp
	* gdb.base/dbx.exp
	* gdb.base/debug-expr.exp
	* gdb.base/define.exp
	* gdb.base/del.exp
	* gdb.base/disabled-location.exp
	* gdb.base/disasm-end-cu.exp
	* gdb.base/disasm-optim.exp
	* gdb.base/display.exp
	* gdb.base/duplicate-bp.exp
	* gdb.base/ena-dis-br.exp
	* gdb.base/ending-run.exp
	* gdb.base/enumval.exp
	* gdb.base/environ.exp
	* gdb.base/eu-strip-infcall.exp
	* gdb.base/eval-avoid-side-effects.exp
	* gdb.base/eval-skip.exp
	* gdb.base/exitsignal.exp
	* gdb.base/expand-psymtabs.exp
	* gdb.base/filesym.exp
	* gdb.base/find-unmapped.exp
	* gdb.base/finish.exp
	* gdb.base/float.exp
	* gdb.base/foll-exec-mode.exp
	* gdb.base/foll-exec.exp
	* gdb.base/foll-fork.exp
	* gdb.base/fortran-sym-case.exp
	* gdb.base/freebpcmd.exp
	* gdb.base/func-ptr.exp
	* gdb.base/func-ptrs.exp
	* gdb.base/funcargs.exp
	* gdb.base/gcore-buffer-overflow.exp
	* gdb.base/gcore-relro-pie.exp
	* gdb.base/gcore-relro.exp
	* gdb.base/gcore.exp
	* gdb.base/gdb1090.exp
	* gdb.base/gdb11530.exp
	* gdb.base/gdb11531.exp
	* gdb.base/gdb1821.exp
	* gdb.base/gdbindex-stabs.exp
	* gdb.base/gdbvars.exp
	* gdb.base/hbreak.exp
	* gdb.base/hbreak2.exp
	* gdb.base/included.exp
	* gdb.base/infcall-input.exp
	* gdb.base/inferior-died.exp
	* gdb.base/infnan.exp
	* gdb.base/info-macros.exp
	* gdb.base/info-os.exp
	* gdb.base/info-proc.exp
	* gdb.base/info-shared.exp
	* gdb.base/info-target.exp
	* gdb.base/infoline.exp
	* gdb.base/interp.exp
	* gdb.base/interrupt.exp
	* gdb.base/jit-reader.exp
	* gdb.base/jit-simple.exp
	* gdb.base/kill-after-signal.exp
	* gdb.base/kill-detach-inferiors-cmd.exp
	* gdb.base/label.exp
	* gdb.base/langs.exp
	* gdb.base/ldbl_e308.exp
	* gdb.base/line-symtabs.exp
	* gdb.base/linespecs.exp
	* gdb.base/list.exp
	* gdb.base/long_long.exp
	* gdb.base/longest-types.exp
	* gdb.base/maint.exp
	* gdb.base/max-value-size.exp
	* gdb.base/memattr.exp
	* gdb.base/mips_pro.exp
	* gdb.base/morestack.exp
	* gdb.base/moribund-step.exp
	* gdb.base/multi-forks.exp
	* gdb.base/nested-addr.exp
	* gdb.base/nextoverexit.exp
	* gdb.base/noreturn-finish.exp
	* gdb.base/noreturn-return.exp
	* gdb.base/nostdlib.exp
	* gdb.base/offsets.exp
	* gdb.base/opaque.exp
	* gdb.base/pc-fp.exp
	* gdb.base/permissions.exp
	* gdb.base/print-symbol-loading.exp
	* gdb.base/prologue-include.exp
	* gdb.base/psymtab.exp
	* gdb.base/ptype.exp
	* gdb.base/random-signal.exp
	* gdb.base/randomize.exp
	* gdb.base/range-stepping.exp
	* gdb.base/readline-ask.exp
	* gdb.base/recpar.exp
	* gdb.base/recurse.exp
	* gdb.base/relational.exp
	* gdb.base/restore.exp
	* gdb.base/return-nodebug.exp
	* gdb.base/return.exp
	* gdb.base/run-after-attach.exp
	* gdb.base/save-bp.exp
	* gdb.base/scope.exp
	* gdb.base/sect-cmd.exp
	* gdb.base/set-lang-auto.exp
	* gdb.base/set-noassign.exp
	* gdb.base/setvar.exp
	* gdb.base/sigall.exp
	* gdb.base/sigbpt.exp
	* gdb.base/siginfo-addr.exp
	* gdb.base/siginfo-infcall.exp
	* gdb.base/siginfo-obj.exp
	* gdb.base/siginfo.exp
	* gdb.base/signals-state-child.exp
	* gdb.base/signest.exp
	* gdb.base/sigstep.exp
	* gdb.base/sizeof.exp
	* gdb.base/skip.exp
	* gdb.base/solib-corrupted.exp
	* gdb.base/solib-nodir.exp
	* gdb.base/solib-search.exp
	* gdb.base/stack-checking.exp
	* gdb.base/stale-infcall.exp
	* gdb.base/stap-probe.exp
	* gdb.base/start.exp
	* gdb.base/step-break.exp
	* gdb.base/step-bt.exp
	* gdb.base/step-line.exp
	* gdb.base/step-over-exit.exp
	* gdb.base/step-over-syscall.exp
	* gdb.base/step-resume-infcall.exp
	* gdb.base/step-test.exp
	* gdb.base/store.exp
	* gdb.base/structs3.exp
	* gdb.base/sym-file.exp
	* gdb.base/symbol-without-target_section.exp
	* gdb.base/term.exp
	* gdb.base/testenv.exp
	* gdb.base/ui-redirect.exp
	* gdb.base/until.exp
	* gdb.base/unwindonsignal.exp
	* gdb.base/value-double-free.exp
	* gdb.base/vla-datatypes.exp
	* gdb.base/vla-ptr.exp
	* gdb.base/vla-sideeffect.exp
	* gdb.base/volatile.exp
	* gdb.base/watch-cond-infcall.exp
	* gdb.base/watch-cond.exp
	* gdb.base/watch-non-mem.exp
	* gdb.base/watch-read.exp
	* gdb.base/watch-vfork.exp
	* gdb.base/watchpoint-cond-gone.exp
	* gdb.base/watchpoint-delete.exp
	* gdb.base/watchpoint-hw-hit-once.exp
	* gdb.base/watchpoint-hw.exp
	* gdb.base/watchpoint-stops-at-right-insn.exp
	* gdb.base/watchpoints.exp
	* gdb.base/wchar.exp
	* gdb.base/whatis-exp.exp
	* gdb.btrace/buffer-size.exp
	* gdb.btrace/data.exp
	* gdb.btrace/delta.exp
	* gdb.btrace/dlopen.exp
	* gdb.btrace/enable.exp
	* gdb.btrace/exception.exp
	* gdb.btrace/function_call_history.exp
	* gdb.btrace/gcore.exp
	* gdb.btrace/instruction_history.exp
	* gdb.btrace/nohist.exp
	* gdb.btrace/reconnect.exp
	* gdb.btrace/record_goto-step.exp
	* gdb.btrace/record_goto.exp
	* gdb.btrace/rn-dl-bind.exp
	* gdb.btrace/segv.exp
	* gdb.btrace/step.exp
	* gdb.btrace/stepi.exp
	* gdb.btrace/tailcall-only.exp
	* gdb.btrace/tailcall.exp
	* gdb.btrace/tsx.exp
	* gdb.btrace/unknown_functions.exp
	* gdb.btrace/vdso.exp
	* gdb.compile/compile-ifunc.exp
	* gdb.compile/compile-ops.exp
	* gdb.compile/compile-print.exp
	* gdb.compile/compile-setjmp.exp
	* gdb.cp/abstract-origin.exp
	* gdb.cp/ambiguous.exp
	* gdb.cp/annota2.exp
	* gdb.cp/annota3.exp
	* gdb.cp/anon-ns.exp
	* gdb.cp/anon-struct.exp
	* gdb.cp/anon-union.exp
	* gdb.cp/arg-reference.exp
	* gdb.cp/baseenum.exp
	* gdb.cp/bool.exp
	* gdb.cp/breakpoint.exp
	* gdb.cp/bs15503.exp
	* gdb.cp/call-c.exp
	* gdb.cp/casts.exp
	* gdb.cp/chained-calls.exp
	* gdb.cp/class2.exp
	* gdb.cp/classes.exp
	* gdb.cp/cmpd-minsyms.exp
	* gdb.cp/converts.exp
	* gdb.cp/cp-relocate.exp
	* gdb.cp/cpcompletion.exp
	* gdb.cp/cpexprs.exp
	* gdb.cp/cplabel.exp
	* gdb.cp/cplusfuncs.exp
	* gdb.cp/cpsizeof.exp
	* gdb.cp/ctti.exp
	* gdb.cp/derivation.exp
	* gdb.cp/destrprint.exp
	* gdb.cp/dispcxx.exp
	* gdb.cp/enum-class.exp
	* gdb.cp/exception.exp
	* gdb.cp/exceptprint.exp
	* gdb.cp/expand-psymtabs-cxx.exp
	* gdb.cp/expand-sals.exp
	* gdb.cp/extern-c.exp
	* gdb.cp/filename.exp
	* gdb.cp/formatted-ref.exp
	* gdb.cp/fpointer.exp
	* gdb.cp/gdb1355.exp
	* gdb.cp/gdb2495.exp
	* gdb.cp/hang.exp
	* gdb.cp/impl-this.exp
	* gdb.cp/infcall-dlopen.exp
	* gdb.cp/inherit.exp
	* gdb.cp/iostream.exp
	* gdb.cp/koenig.exp
	* gdb.cp/local.exp
	* gdb.cp/m-data.exp
	* gdb.cp/m-static.exp
	* gdb.cp/mb-ctor.exp
	* gdb.cp/mb-inline.exp
	* gdb.cp/mb-templates.exp
	* gdb.cp/member-name.exp
	* gdb.cp/member-ptr.exp
	* gdb.cp/meth-typedefs.exp
	* gdb.cp/method.exp
	* gdb.cp/method2.exp
	* gdb.cp/minsym-fallback.exp
	* gdb.cp/misc.exp
	* gdb.cp/namelessclass.exp
	* gdb.cp/namespace-enum.exp
	* gdb.cp/namespace-nested-import.exp
	* gdb.cp/namespace.exp
	* gdb.cp/nextoverthrow.exp
	* gdb.cp/no-dmgl-verbose.exp
	* gdb.cp/non-trivial-retval.exp
	* gdb.cp/noparam.exp
	* gdb.cp/nsdecl.exp
	* gdb.cp/nsimport.exp
	* gdb.cp/nsnested.exp
	* gdb.cp/nsnoimports.exp
	* gdb.cp/nsrecurs.exp
	* gdb.cp/nsstress.exp
	* gdb.cp/nsusing.exp
	* gdb.cp/operator.exp
	* gdb.cp/oranking.exp
	* gdb.cp/overload-const.exp
	* gdb.cp/overload.exp
	* gdb.cp/ovldbreak.exp
	* gdb.cp/ovsrch.exp
	* gdb.cp/paren-type.exp
	* gdb.cp/parse-lang.exp
	* gdb.cp/pass-by-ref.exp
	* gdb.cp/pr-1023.exp
	* gdb.cp/pr-1210.exp
	* gdb.cp/pr-574.exp
	* gdb.cp/pr10687.exp
	* gdb.cp/pr12028.exp
	* gdb.cp/pr17132.exp
	* gdb.cp/pr17494.exp
	* gdb.cp/pr9067.exp
	* gdb.cp/pr9167.exp
	* gdb.cp/pr9631.exp
	* gdb.cp/printmethod.exp
	* gdb.cp/psmang.exp
	* gdb.cp/psymtab-parameter.exp
	* gdb.cp/ptype-cv-cp.exp
	* gdb.cp/ptype-flags.exp
	* gdb.cp/re-set-overloaded.exp
	* gdb.cp/ref-types.exp
	* gdb.cp/rtti.exp
	* gdb.cp/scope-err.exp
	* gdb.cp/shadow.exp
	* gdb.cp/smartp.exp
	* gdb.cp/static-method.exp
	* gdb.cp/static-print-quit.exp
	* gdb.cp/temargs.exp
	* gdb.cp/templates.exp
	* gdb.cp/try_catch.exp
	* gdb.cp/typedef-operator.exp
	* gdb.cp/typeid.exp
	* gdb.cp/userdef.exp
	* gdb.cp/using-crash.exp
	* gdb.cp/var-tag.exp
	* gdb.cp/virtbase.exp
	* gdb.cp/virtfunc.exp
	* gdb.cp/virtfunc2.exp
	* gdb.cp/vla-cxx.exp
	* gdb.disasm/t01_mov.exp
	* gdb.disasm/t02_mova.exp
	* gdb.disasm/t03_add.exp
	* gdb.disasm/t04_sub.exp
	* gdb.disasm/t05_cmp.exp
	* gdb.disasm/t06_ari2.exp
	* gdb.disasm/t07_ari3.exp
	* gdb.disasm/t08_or.exp
	* gdb.disasm/t09_xor.exp
	* gdb.disasm/t10_and.exp
	* gdb.disasm/t11_logs.exp
	* gdb.disasm/t12_bit.exp
	* gdb.disasm/t13_otr.exp
	* gdb.dlang/circular.exp
	* gdb.dwarf2/arr-stride.exp
	* gdb.dwarf2/arr-subrange.exp
	* gdb.dwarf2/atomic-type.exp
	* gdb.dwarf2/bad-regnum.exp
	* gdb.dwarf2/bitfield-parent-optimized-out.exp
	* gdb.dwarf2/callframecfa.exp
	* gdb.dwarf2/clztest.exp
	* gdb.dwarf2/corrupt.exp
	* gdb.dwarf2/data-loc.exp
	* gdb.dwarf2/dup-psym.exp
	* gdb.dwarf2/dw2-anon-mptr.exp
	* gdb.dwarf2/dw2-anonymous-func.exp
	* gdb.dwarf2/dw2-bad-mips-linkage-name.exp
	* gdb.dwarf2/dw2-bad-unresolved.exp
	* gdb.dwarf2/dw2-basic.exp
	* gdb.dwarf2/dw2-canonicalize-type.exp
	* gdb.dwarf2/dw2-case-insensitive.exp
	* gdb.dwarf2/dw2-common-block.exp
	* gdb.dwarf2/dw2-compdir-oldgcc.exp
	* gdb.dwarf2/dw2-compressed.exp
	* gdb.dwarf2/dw2-const.exp
	* gdb.dwarf2/dw2-cp-infcall-ref-static.exp
	* gdb.dwarf2/dw2-cu-size.exp
	* gdb.dwarf2/dw2-dup-frame.exp
	* gdb.dwarf2/dw2-entry-value.exp
	* gdb.dwarf2/dw2-icycle.exp
	* gdb.dwarf2/dw2-ifort-parameter.exp
	* gdb.dwarf2/dw2-inline-break.exp
	* gdb.dwarf2/dw2-inline-param.exp
	* gdb.dwarf2/dw2-intercu.exp
	* gdb.dwarf2/dw2-intermix.exp
	* gdb.dwarf2/dw2-lexical-block-bare.exp
	* gdb.dwarf2/dw2-linkage-name-trust.exp
	* gdb.dwarf2/dw2-minsym-in-cu.exp
	* gdb.dwarf2/dw2-noloc.exp
	* gdb.dwarf2/dw2-op-call.exp
	* gdb.dwarf2/dw2-op-out-param.exp
	* gdb.dwarf2/dw2-opt-structptr.exp
	* gdb.dwarf2/dw2-param-error.exp
	* gdb.dwarf2/dw2-producer.exp
	* gdb.dwarf2/dw2-ranges-base.exp
	* gdb.dwarf2/dw2-ref-missing-frame.exp
	* gdb.dwarf2/dw2-reg-undefined.exp
	* gdb.dwarf2/dw2-regno-invalid.exp
	* gdb.dwarf2/dw2-restore.exp
	* gdb.dwarf2/dw2-restrict.exp
	* gdb.dwarf2/dw2-single-line-discriminators.exp
	* gdb.dwarf2/dw2-strp.exp
	* gdb.dwarf2/dw2-undefined-ret-addr.exp
	* gdb.dwarf2/dw2-unresolved.exp
	* gdb.dwarf2/dw2-var-zero-addr.exp
	* gdb.dwarf2/dw4-sig-types.exp
	* gdb.dwarf2/dwz.exp
	* gdb.dwarf2/dynarr-ptr.exp
	* gdb.dwarf2/enum-type.exp
	* gdb.dwarf2/gdb-index.exp
	* gdb.dwarf2/implptr-64bit.exp
	* gdb.dwarf2/implptr-optimized-out.exp
	* gdb.dwarf2/implptr.exp
	* gdb.dwarf2/implref-array.exp
	* gdb.dwarf2/implref-const.exp
	* gdb.dwarf2/implref-global.exp
	* gdb.dwarf2/implref-struct.exp
	* gdb.dwarf2/mac-fileno.exp
	* gdb.dwarf2/main-subprogram.exp
	* gdb.dwarf2/member-ptr-forwardref.exp
	* gdb.dwarf2/method-ptr.exp
	* gdb.dwarf2/missing-sig-type.exp
	* gdb.dwarf2/nonvar-access.exp
	* gdb.dwarf2/opaque-type-lookup.exp
	* gdb.dwarf2/pieces-optimized-out.exp
	* gdb.dwarf2/pieces.exp
	* gdb.dwarf2/pr10770.exp
	* gdb.dwarf2/pr13961.exp
	* gdb.dwarf2/staticvirtual.exp
	* gdb.dwarf2/subrange.exp
	* gdb.dwarf2/symtab-producer.exp
	* gdb.dwarf2/trace-crash.exp
	* gdb.dwarf2/typeddwarf.exp
	* gdb.dwarf2/valop.exp
	* gdb.dwarf2/watch-notconst.exp
	* gdb.fortran/array-element.exp
	* gdb.fortran/charset.exp
	* gdb.fortran/common-block.exp
	* gdb.fortran/complex.exp
	* gdb.fortran/derived-type-function.exp
	* gdb.fortran/derived-type.exp
	* gdb.fortran/logical.exp
	* gdb.fortran/module.exp
	* gdb.fortran/multi-dim.exp
	* gdb.fortran/nested-funcs.exp
	* gdb.fortran/print-formatted.exp
	* gdb.fortran/subarray.exp
	* gdb.fortran/vla-alloc-assoc.exp
	* gdb.fortran/vla-datatypes.exp
	* gdb.fortran/vla-history.exp
	* gdb.fortran/vla-ptr-info.exp
	* gdb.fortran/vla-ptype-sub.exp
	* gdb.fortran/vla-ptype.exp
	* gdb.fortran/vla-sizeof.exp
	* gdb.fortran/vla-type.exp
	* gdb.fortran/vla-value-sub-arbitrary.exp
	* gdb.fortran/vla-value-sub-finish.exp
	* gdb.fortran/vla-value-sub.exp
	* gdb.fortran/vla-value.exp
	* gdb.fortran/whatis_type.exp
	* gdb.go/chan.exp
	* gdb.go/handcall.exp
	* gdb.go/hello.exp
	* gdb.go/integers.exp
	* gdb.go/methods.exp
	* gdb.go/package.exp
	* gdb.go/strings.exp
	* gdb.go/types.exp
	* gdb.go/unsafe.exp
	* gdb.guile/scm-arch.exp
	* gdb.guile/scm-block.exp
	* gdb.guile/scm-breakpoint.exp
	* gdb.guile/scm-cmd.exp
	* gdb.guile/scm-disasm.exp
	* gdb.guile/scm-equal.exp
	* gdb.guile/scm-frame-args.exp
	* gdb.guile/scm-frame-inline.exp
	* gdb.guile/scm-frame.exp
	* gdb.guile/scm-iterator.exp
	* gdb.guile/scm-math.exp
	* gdb.guile/scm-objfile.exp
	* gdb.guile/scm-ports.exp
	* gdb.guile/scm-symbol.exp
	* gdb.guile/scm-symtab.exp
	* gdb.guile/scm-value-cc.exp
	* gdb.guile/types-module.exp
	* gdb.linespec/break-ask.exp
	* gdb.linespec/cpexplicit.exp
	* gdb.linespec/explicit.exp
	* gdb.linespec/keywords.exp
	* gdb.linespec/linespec.exp
	* gdb.linespec/ls-dollar.exp
	* gdb.linespec/ls-errs.exp
	* gdb.linespec/skip-two.exp
	* gdb.linespec/thread.exp
	* gdb.mi/mi-async.exp
	* gdb.mi/mi-basics.exp
	* gdb.mi/mi-break.exp
	* gdb.mi/mi-catch-load.exp
	* gdb.mi/mi-cli.exp
	* gdb.mi/mi-cmd-param-changed.exp
	* gdb.mi/mi-console.exp
	* gdb.mi/mi-detach.exp
	* gdb.mi/mi-disassemble.exp
	* gdb.mi/mi-eval.exp
	* gdb.mi/mi-file-transfer.exp
	* gdb.mi/mi-file.exp
	* gdb.mi/mi-fill-memory.exp
	* gdb.mi/mi-inheritance-syntax-error.exp
	* gdb.mi/mi-linespec-err-cp.exp
	* gdb.mi/mi-logging.exp
	* gdb.mi/mi-memory-changed.exp
	* gdb.mi/mi-read-memory.exp
	* gdb.mi/mi-record-changed.exp
	* gdb.mi/mi-reg-undefined.exp
	* gdb.mi/mi-regs.exp
	* gdb.mi/mi-return.exp
	* gdb.mi/mi-reverse.exp
	* gdb.mi/mi-simplerun.exp
	* gdb.mi/mi-solib.exp
	* gdb.mi/mi-stack.exp
	* gdb.mi/mi-stepi.exp
	* gdb.mi/mi-syn-frame.exp
	* gdb.mi/mi-until.exp
	* gdb.mi/mi-var-block.exp
	* gdb.mi/mi-var-child.exp
	* gdb.mi/mi-var-cmd.exp
	* gdb.mi/mi-var-cp.exp
	* gdb.mi/mi-var-display.exp
	* gdb.mi/mi-var-invalidate.exp
	* gdb.mi/mi-var-list-children-invalid-grandchild.exp
	* gdb.mi/mi-vla-fortran.exp
	* gdb.mi/mi-watch.exp
	* gdb.mi/mi2-var-child.exp
	* gdb.mi/user-selected-context-sync.exp
	* gdb.modula2/unbounded-array.exp
	* gdb.multi/dummy-frame-restore.exp
	* gdb.multi/multi-arch-exec.exp
	* gdb.multi/multi-arch.exp
	* gdb.multi/tids.exp
	* gdb.multi/watchpoint-multi.exp
	* gdb.opencl/callfuncs.exp
	* gdb.opencl/convs_casts.exp
	* gdb.opencl/datatypes.exp
	* gdb.opencl/operators.exp
	* gdb.opencl/vec_comps.exp
	* gdb.opt/clobbered-registers-O2.exp
	* gdb.opt/inline-break.exp
	* gdb.opt/inline-bt.exp
	* gdb.opt/inline-cmds.exp
	* gdb.opt/inline-locals.exp
	* gdb.pascal/case-insensitive-symbols.exp
	* gdb.pascal/floats.exp
	* gdb.pascal/gdb11492.exp
	* gdb.python/lib-types.exp
	* gdb.python/py-arch.exp
	* gdb.python/py-as-string.exp
	* gdb.python/py-bad-printers.exp
	* gdb.python/py-block.exp
	* gdb.python/py-breakpoint-create-fail.exp
	* gdb.python/py-breakpoint.exp
	* gdb.python/py-caller-is.exp
	* gdb.python/py-cmd.exp
	* gdb.python/py-explore-cc.exp
	* gdb.python/py-explore.exp
	* gdb.python/py-finish-breakpoint.exp
	* gdb.python/py-finish-breakpoint2.exp
	* gdb.python/py-frame-args.exp
	* gdb.python/py-frame-inline.exp
	* gdb.python/py-frame.exp
	* gdb.python/py-framefilter-mi.exp
	* gdb.python/py-infthread.exp
	* gdb.python/py-lazy-string.exp
	* gdb.python/py-linetable.exp
	* gdb.python/py-mi-events.exp
	* gdb.python/py-mi-objfile.exp
	* gdb.python/py-mi.exp
	* gdb.python/py-objfile.exp
	* gdb.python/py-pp-integral.exp
	* gdb.python/py-pp-maint.exp
	* gdb.python/py-pp-re-notag.exp
	* gdb.python/py-pp-registration.exp
	* gdb.python/py-recurse-unwind.exp
	* gdb.python/py-strfns.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-symtab.exp
	* gdb.python/py-sync-interp.exp
	* gdb.python/py-typeprint.exp
	* gdb.python/py-unwind-maint.exp
	* gdb.python/py-unwind.exp
	* gdb.python/py-value-cc.exp
	* gdb.python/py-xmethods.exp
	* gdb.reverse/amd64-tailcall-reverse.exp
	* gdb.reverse/break-precsave.exp
	* gdb.reverse/break-reverse.exp
	* gdb.reverse/consecutive-precsave.exp
	* gdb.reverse/consecutive-reverse.exp
	* gdb.reverse/finish-precsave.exp
	* gdb.reverse/finish-reverse-bkpt.exp
	* gdb.reverse/finish-reverse.exp
	* gdb.reverse/fstatat-reverse.exp
	* gdb.reverse/getresuid-reverse.exp
	* gdb.reverse/i386-precsave.exp
	* gdb.reverse/i386-reverse.exp
	* gdb.reverse/i386-sse-reverse.exp
	* gdb.reverse/i387-env-reverse.exp
	* gdb.reverse/i387-stack-reverse.exp
	* gdb.reverse/insn-reverse.exp
	* gdb.reverse/machinestate-precsave.exp
	* gdb.reverse/machinestate.exp
	* gdb.reverse/next-reverse-bkpt-over-sr.exp
	* gdb.reverse/pipe-reverse.exp
	* gdb.reverse/readv-reverse.exp
	* gdb.reverse/recvmsg-reverse.exp
	* gdb.reverse/rerun-prec.exp
	* gdb.reverse/s390-mvcle.exp
	* gdb.reverse/step-precsave.exp
	* gdb.reverse/step-reverse.exp
	* gdb.reverse/time-reverse.exp
	* gdb.reverse/until-precsave.exp
	* gdb.reverse/until-reverse.exp
	* gdb.reverse/waitpid-reverse.exp
	* gdb.reverse/watch-precsave.exp
	* gdb.reverse/watch-reverse.exp
	* gdb.rust/generics.exp
	* gdb.rust/methods.exp
	* gdb.rust/modules.exp
	* gdb.rust/simple.exp
	* gdb.server/connect-with-no-symbol-file.exp
	* gdb.server/ext-attach.exp
	* gdb.server/ext-restart.exp
	* gdb.server/ext-wrapper.exp
	* gdb.server/file-transfer.exp
	* gdb.server/server-exec-info.exp
	* gdb.server/server-kill.exp
	* gdb.server/server-mon.exp
	* gdb.server/wrapper.exp
	* gdb.stabs/exclfwd.exp
	* gdb.stabs/gdb11479.exp
	* gdb.threads/clone-new-thread-event.exp
	* gdb.threads/corethreads.exp
	* gdb.threads/current-lwp-dead.exp
	* gdb.threads/dlopen-libpthread.exp
	* gdb.threads/gcore-thread.exp
	* gdb.threads/sigstep-threads.exp
	* gdb.threads/watchpoint-fork.exp
	* gdb.trace/actions-changed.exp
	* gdb.trace/backtrace.exp
	* gdb.trace/change-loc.exp
	* gdb.trace/circ.exp
	* gdb.trace/collection.exp
	* gdb.trace/disconnected-tracing.exp
	* gdb.trace/ftrace.exp
	* gdb.trace/mi-trace-frame-collected.exp
	* gdb.trace/mi-trace-unavailable.exp
	* gdb.trace/mi-traceframe-changed.exp
	* gdb.trace/mi-tsv-changed.exp
	* gdb.trace/no-attach-trace.exp
	* gdb.trace/passc-dyn.exp
	* gdb.trace/qtro.exp
	* gdb.trace/range-stepping.exp
	* gdb.trace/read-memory.exp
	* gdb.trace/save-trace.exp
	* gdb.trace/signal.exp
	* gdb.trace/status-stop.exp
	* gdb.trace/tfile.exp
	* gdb.trace/trace-break.exp
	* gdb.trace/trace-buffer-size.exp
	* gdb.trace/trace-condition.exp
	* gdb.trace/tracefile-pseudo-reg.exp
	* gdb.trace/tstatus.exp
	* gdb.trace/unavailable.exp
	* gdb.trace/while-dyn.exp
	* gdb.trace/while-stepping.exp


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS16/GAS: Disallow EXTEND delay-slot scheduling
@ 2016-12-23 21:34 sergiodj+buildbot
  2016-12-28 12:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 21:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 645c455650ed35460afdacb078c7c58308607fbe ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 645c455650ed35460afdacb078c7c58308607fbe

MIPS16/GAS: Disallow EXTEND delay-slot scheduling

Do not allow any explicitly coded EXTEND instruction to be automatically
scheduled into a jump delay slot, as an EXTEND prefix is coupled with
the next regular MIPS16 instruction and therefore swapping it with a
jump would change program's semantics; EXTEND is not architecturally
allowed to be present in a jump delay slot anyway.

	opcodes/
	* mips16-opc.c (mips16_opcodes): Set NODS in `pinfo' for
	"extend".

	gas/
	* testsuite/gas/mips/mips16-extend-swap.d: New test.
	* testsuite/gas/mips/mips16-extend-swap.s: New test source.
	* testsuite/gas/mips/mips.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS16: Simplify extended operand handling
@ 2016-12-23 22:22 sergiodj+buildbot
  2016-12-29  3:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 22:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdd152861ce75c36828904cf3d10f8ce14da6cf5 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: bdd152861ce75c36828904cf3d10f8ce14da6cf5

MIPS16: Simplify extended operand handling

Simplify extended operand handling and only specially process immediates
which require bit shuffling, using the generic operand insertion and
extraction handlers for the '<' (5-bit shift amount) operand code in
particular.  Require the least significant bit of all extended operand
forms to be (artificially) set to 0 for their special processing to
trigger.

	gas/
	* config/tc-mips.c (mips16_immed): Limit `mips16_immed_extend'
	use to operands whose LSB position is zero.

	opcodes/
	* mips-dis.c (print_mips16_insn_arg): Simplify processing of
	extended operands.
	* mips16-opc.c (decode_mips16_operand): Switch the extended
	form of the `<' operand type to LSB position 22.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS16: Reassign `0' and `4' operand codes
@ 2016-12-24  0:33 sergiodj+buildbot
  2016-12-29  0:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-24  0:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d8722d7641d234dcd3d1f2254fbc5d9cf234e4e6 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: d8722d7641d234dcd3d1f2254fbc5d9cf234e4e6

MIPS16: Reassign `0' and `4' operand codes

Replace `0' and `4' operand codes with `.' and `F' respectively to free
up the `0'-`4' consecutive range.  No functional change.

	gas/
	* config/tc-mips.c (mips16_macro_build): Replace `0' and `4'
	operand codes with `.' and `F' respectively.
	(mips16_macro): Likewise.

	include/
	* opcode/mips.h: Replace `0' and `4' operand codes with `.' and
	`F' respectively.

	opcodes/
	* mips16-opc.c (decode_mips16_operand): Replace `0' and `4'
	operand codes with `.' and `F' respectively.
	(mips16_opcodes): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Remove EI_ABIVERSION 5 allocation for PT_GNU_STACK support
@ 2016-12-24  3:33 sergiodj+buildbot
  2016-12-29 13:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-24  3:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d4f40e041ce7c8c7c8e50f957e0440b64ab7e95 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 4d4f40e041ce7c8c7c8e50f957e0440b64ab7e95

MIPS/BFD: Remove EI_ABIVERSION 5 allocation for PT_GNU_STACK support

Revert commit 17733f5be961 ("Increment the ABIVERSION to 5 for MIPS
objects with non-executable stacks.") and remove EI_ABIVERSION 5
allocation for PT_GNU_STACK support, which has not made it to glibc
and will be reassigned.

	bfd/
	* bfd/elfxx-mips.c (_bfd_mips_post_process_headers): Revert
	2016-02-23 change and remove EI_ABIVERSION 5 support.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] dynrelro section for read-only dynamic symbols copied into executable
@ 2016-12-26  6:54 sergiodj+buildbot
  2016-12-30  1:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-26  6:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5474d94f03aedba2f832006dc7d680cc15792a7b ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 5474d94f03aedba2f832006dc7d680cc15792a7b

dynrelro section for read-only dynamic symbols copied into executable

Variables defined in shared libraries are copied into an executable's
.bss section when code in the executable is non-PIC and thus would
require dynamic text relocations to access the variable directly in
the shared library.  Recent x86 toolchains also copy variables into
the executable to gain a small speed improvement.

The problem is that if the variable was originally read-only, the copy
in .bss is writable, potentially opening a security hole.  This patch
cures that problem by putting the copy in a section that becomes
read-only after ld.so relocation, provided -z relro is in force.

The patch also fixes a microblaze linker segfault on attempting to
use dynamic bss variables.

bfd/
	PR ld/20995
	* elf-bfd.h (struct elf_link_hash_table): Add sdynrelro and
	sreldynrelro.
	(struct elf_backend_data): Add want_dynrelro.
	* elfxx-target.h (elf_backend_want_dynrelro): Define.
	(elfNN_bed): Update initializer.
	* elflink.c (_bfd_elf_create_dynamic_sections): Create
	sdynrelro and sreldynrelro sections.
	* elf32-arm.c (elf32_arm_adjust_dynamic_symbol): Place variables
	copied into the executable from read-only sections into sdynrelro.
	(elf32_arm_size_dynamic_sections): Handle sdynrelro.
	(elf32_arm_finish_dynamic_symbol): Select sreldynrelro for
	dynamic relocs in sdynrelro.
	(elf_backend_want_dynrelro): Define.
	* elf32-hppa.c (elf32_hppa_adjust_dynamic_symbol)
	(elf32_hppa_size_dynamic_sections, elf32_hppa_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elf32-i386.c (elf_i386_adjust_dynamic_symbol)
	(elf_i386_size_dynamic_sections, elf_i386_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elf32-metag.c (elf_metag_adjust_dynamic_symbol)
	(elf_metag_size_dynamic_sections, elf_metag_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elf32-microblaze.c (microblaze_elf_adjust_dynamic_symbol)
	(microblaze_elf_size_dynamic_sections)
	(microblaze_elf_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elf32-nios2.c (nios2_elf32_finish_dynamic_symbol)
	(nios2_elf32_adjust_dynamic_symbol)
	(nios2_elf32_size_dynamic_sections)
	(elf_backend_want_dynrelro): As above.
	* elf32-or1k.c (or1k_elf_finish_dynamic_symbol)
	(or1k_elf_adjust_dynamic_symbol, or1k_elf_size_dynamic_sections)
	(elf_backend_want_dynrelro): As above.
	* elf32-ppc.c (ppc_elf_adjust_dynamic_symbol)
	(ppc_elf_size_dynamic_sections, ppc_elf_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elf32-s390.c (elf_s390_adjust_dynamic_symbol)
	(elf_s390_size_dynamic_sections, elf_s390_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elf32-tic6x.c (elf32_tic6x_adjust_dynamic_symbol)
	(elf32_tic6x_size_dynamic_sections)
	(elf32_tic6x_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elf32-tilepro.c (tilepro_elf_adjust_dynamic_symbol)
	(tilepro_elf_size_dynamic_sections)
	(tilepro_elf_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elf64-ppc.c (ppc64_elf_adjust_dynamic_symbol)
	(ppc64_elf_size_dynamic_sections, ppc64_elf_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elf64-s390.c (elf_s390_adjust_dynamic_symbol)
	(elf_s390_size_dynamic_sections, elf_s390_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elf64-x86-64.c (elf_x86_64_adjust_dynamic_symbol)
	(elf_x86_64_size_dynamic_sections)
	(elf_x86_64_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elfnn-aarch64.c (elfNN_aarch64_adjust_dynamic_symbol)
	(elfNN_aarch64_size_dynamic_sections)
	(elfNN_aarch64_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elfnn-riscv.c (riscv_elf_adjust_dynamic_symbol)
	(riscv_elf_size_dynamic_sections, riscv_elf_finish_dynamic_symbol)
	(elf_backend_want_dynrelro): As above.
	* elfxx-mips.c (_bfd_mips_elf_adjust_dynamic_symbol)
	(_bfd_mips_elf_size_dynamic_sections)
	(_bfd_mips_vxworks_finish_dynamic_symbol): As above.
	* elfxx-sparc.c (_bfd_sparc_elf_adjust_dynamic_symbol)
	(_bfd_sparc_elf_size_dynamic_sections)
	(_bfd_sparc_elf_finish_dynamic_symbol): As above.
	* elfxx-tilegx.c (tilegx_elf_adjust_dynamic_symbol)
	(tilegx_elf_size_dynamic_sections)
	(tilegx_elf_finish_dynamic_symbol): As above.
	* elf32-mips.c (elf_backend_want_dynrelro): Define.
	* elf64-mips.c (elf_backend_want_dynrelro): Define.
	* elf32-sparc.c (elf_backend_want_dynrelro): Define.
	* elf64-sparc.c (elf_backend_want_dynrelro): Define.
	* elf32-tilegx.c (elf_backend_want_dynrelro): Define.
	* elf64-tilegx.c (elf_backend_want_dynrelro): Define.
	* elf32-microblaze.c (microblaze_elf_adjust_dynamic_symbol): Tidy.
	(microblaze_elf_size_dynamic_sections): Handle sdynbss.
	* elf32-nios2.c (nios2_elf32_size_dynamic_sections): Make use
	of linker shortcuts to dynamic sections rather than comparing
	names.  Correctly set "got" flag.
ld/
	PR ld/20995
	* testsuite/ld-arm/farcall-mixed-app-v5.d: Update to suit changed
	stub hash table traversal caused by section id increment.  Accept
	the previous output too.
	* testsuite/ld-arm/farcall-mixed-app.d: Likewise.
	* testsuite/ld-arm/farcall-mixed-lib-v4t.d: Likewise.
	* testsuite/ld-arm/farcall-mixed-lib.d: Likewise.
	* testsuite/ld-elf/pr20995a.s, * testsuite/ld-elf/pr20995b.s,
	* testsuite/ld-elf/pr20995.r: New test.
	* testsuite/ld-elf/elf.exp: Run it.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Check bfd support for bfd_mips_elf_get_abiflags in mips make rule
@ 2016-12-28 13:44 sergiodj+buildbot
  2016-12-30 12:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-28 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fa6f7cee7dedb600799234b1e2d52c5b0da8f96 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 0fa6f7cee7dedb600799234b1e2d52c5b0da8f96

Check bfd support for bfd_mips_elf_get_abiflags in mips make rule

The previous scheme with a dependency in opcodes on libbfd.la
broke "make distclean".

	* configure.ac: Revert 2016-12-23.
	* Makefile.am: Likewise.
	(MIPS_DEFS): Define.
	(mips-dis.lo): Add rule.
	* Makefile.in: Regenerate.
	* aclocal.m4: Regenerate.
	* config.in: Regenerate.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PRU Opcode Port
@ 2016-12-31  4:19 sergiodj+buildbot
  2016-12-31 15:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-31  4:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 111468496477e97c9414d2d54f97bfdaa380f794 ***

Author: Dimitar Dimitrov <dimitar@dinux.eu>
Branch: master
Commit: 111468496477e97c9414d2d54f97bfdaa380f794

PRU Opcode Port

opcodes/
	* Makefile.am: Add PRU source files.
	* configure.ac: Add PRU target.
	* disassemble.c (disassembler): Register PRU arch.
	* pru-dis.c: New file.
	* pru-opc.c: New file.
	* Makefile.in: Regenerate.
	* configure: Regenerate.

Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Create sdynrelro for elfn32 mips too
@ 2016-12-31  9:11 sergiodj+buildbot
  2016-12-31 19:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2016-12-31  9:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7aba156196caf59117741eae5e93b578d0b59f4 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: b7aba156196caf59117741eae5e93b578d0b59f4

Create sdynrelro for elfn32 mips too

	* elfn32-mips.c (elf_backend_want_dynrelro): Define.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't make symbols dynamic other than undef weak
@ 2017-01-04  1:22 sergiodj+buildbot
  2017-01-04 11:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  1:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 595e0a47f57b414843261303b8aa5036fd1fa1e3 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 595e0a47f57b414843261303b8aa5036fd1fa1e3

Don't make symbols dynamic other than undef weak

Fixes: tmpdir/pr14525: symbol lookup error: tmpdir/pr14525: undefined
symbol: __executable_start
FAIL: PIE PR ld/14525

	* elf32-hppa.c (ensure_undef_weak_dynamic): New function.
	(allocate_plt_static, allocate_dynrelocs): Use it.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix compile time warning about using a possibly uninitialised variable.
@ 2017-01-04  1:38 sergiodj+buildbot
  2017-01-04 23:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  1:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09fe2662a708aa4da665bcaf942b5529e6809220 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 09fe2662a708aa4da665bcaf942b5529e6809220

Fix compile time warning about using a possibly uninitialised variable.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Regen opcodes cgen files
@ 2017-01-04  2:06 sergiodj+buildbot
  2017-01-04 15:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  2:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f47b0d4a49facbfa5c2f0971474593df0a854547 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: f47b0d4a49facbfa5c2f0971474593df0a854547

Regen opcodes cgen files

	* epiphany-desc.h: Regenerate.
	* epiphany-opc.h: Regenerate.
	* fr30-desc.h: Regenerate.
	* fr30-opc.h: Regenerate.
	* frv-desc.h: Regenerate.
	* frv-opc.h: Regenerate.
	* ip2k-desc.h: Regenerate.
	* ip2k-opc.h: Regenerate.
	* iq2000-desc.h: Regenerate.
	* iq2000-opc.h: Regenerate.
	* lm32-desc.h: Regenerate.
	* lm32-opc.h: Regenerate.
	* m32c-desc.h: Regenerate.
	* m32c-opc.h: Regenerate.
	* m32r-desc.h: Regenerate.
	* m32r-opc.h: Regenerate.
	* mep-desc.h: Regenerate.
	* mep-opc.h: Regenerate.
	* mt-desc.h: Regenerate.
	* mt-opc.h: Regenerate.
	* or1k-desc.h: Regenerate.
	* or1k-opc.h: Regenerate.
	* xc16x-desc.h: Regenerate.
	* xc16x-opc.h: Regenerate.
	* xstormy16-desc.h: Regenerate.
	* xstormy16-opc.h: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add fall through comment.
@ 2017-01-04  3:11 sergiodj+buildbot
  2017-01-05  7:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  3:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b52d3cfcfb472263eca181da37dfc0377978acba ***

Author: Dilyan Palauzov <dilyan.palauzov@aegee.org>
Branch: master
Commit: b52d3cfcfb472263eca181da37dfc0377978acba

Add fall through comment.

	* riscv-dis.c (print_insn_args): Add fall through comment.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for the Q extension to the RISCV ISA.
@ 2017-01-04  3:42 sergiodj+buildbot
  2017-01-05 14:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  3:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc917fd93d2a836adfd61b91df021cf835e88fd1 ***

Author: Kito Cheng <kito.cheng@gmail.com>
Branch: master
Commit: cc917fd93d2a836adfd61b91df021cf835e88fd1

Add support for the Q extension to the RISCV ISA.

gas    * config/tc-riscv.c (riscv_set_arch): Whitelist the "q" ISA
        extension.
        (riscv_after_parse_args): Set FLOAT_ABI_QUAD when the Q ISA is
        enabled and no other ABI is specified.

include * opcode/riscv-opc.h: Add support for the "q" ISA extension.

opcodes * riscv-opc.c (riscv-opcodes): Add support for the "q" ISA
        extension.
        * riscv-opcodes/all-opcodes: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] bfd: alpha: Fix crash caused by double free with --no-keep-memory
@ 2017-01-04  3:56 sergiodj+buildbot
  2017-01-05 18:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  3:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae4fda663812129df67e3a70691787060242c0f9 ***

Author: James Clarke <jrtc27@jrtc27.com>
Branch: master
Commit: ae4fda663812129df67e3a70691787060242c0f9

bfd: alpha: Fix crash caused by double free with --no-keep-memory

Without this, ld has been seen to crash in libc when freeing tsec_free:

*** Error in `/usr/bin/ld': double free or corruption (!prev): 0x0000000120ceb6a0 ***

_bfd_elf_link_read_relocs will always return the cached value if
present, even if keep_memory is false, therefore setting tsec_free to
NULL only when keep_memory is true is not sufficient.

	* elf64-alpha.c (elf64_alpha_relax_opt_call): Don't set tsec_free
	if relocs are cached.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix an internal error on writing pieced value
@ 2017-01-04 10:10 sergiodj+buildbot
  2017-01-05 22:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-04 10:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2aaaf250e80afb4a5c66fb0b7801e24cc5c4e680 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 2aaaf250e80afb4a5c66fb0b7801e24cc5c4e680

Fix an internal error on writing pieced value

In ee40d8d (Move computed value's frame id to piece_closure), I only
updated read_pieced_value to use frame_id from piece_closure, but
forgot to update write_pieced_value, so it causes the following
internal error on arm-linux,

set variable l = 4^M
gdb/git/gdb/value.c:1579: internal-error: frame_id* deprecated_value_next_frame_id_hack(value*): Assertion `value->lval == lval_register' failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
Quit this debugging session? (y or n) FAIL: gdb.base/store.exp: var longest l; setting l to 4 (GDB internal error)

This patch fixes the internal error.

gdb:

2017-01-04  Yao Qi  <yao.qi@linaro.org>

	* dwarf2loc.c (write_pieced_value): Don't use VALUE_FRAME_ID (to),
	use c->frame_id when the piece location is DWARF_VALUE_REGISTER.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Sync libiberty from gcc
@ 2017-01-04 14:42 sergiodj+buildbot
  2017-01-06 10:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-04 14:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e495212d229d58eb4d70c94d7f828a04c386c3b2 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: e495212d229d58eb4d70c94d7f828a04c386c3b2

Sync libiberty from gcc

Picks up copyright year update and other recent fixes.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] update-copyright.py for binutils
@ 2017-01-04 14:57 sergiodj+buildbot
  2017-01-06 14:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-04 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c2a23b23e9ca7015acadbbc7a12c665791c8337 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 7c2a23b23e9ca7015acadbbc7a12c665791c8337

update-copyright.py for binutils

This is a modified form of gcc's contrib/update-copyright.py.

	* update-copyright.py: New file.
	* add-log.el: Update copyright year range.
	* texi2pod.pl: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use correct OSABI constant for FreeBSD/mips binaries.
@ 2017-01-04 20:32 sergiodj+buildbot
  2017-01-06 22:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-04 20:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c988ac1de5bc0efec2022fc6ce7d13b24e540099 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: c988ac1de5bc0efec2022fc6ce7d13b24e540099

Use correct OSABI constant for FreeBSD/mips binaries.

gdb/ChangeLog:

	* mips-fbsd-tdep.c (_initialize_mips_fbsd_tdep): Use
	GDB_OSABI_FREEBSD instead of GDB_OSABI_FREEBSD_ELF.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Five fixes, for fcsel, fcvtz, fminnm, mls, and non-widening mul.
@ 2017-01-05  0:23 sergiodj+buildbot
  2017-01-07  3:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-05  0:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0386d4d54d2cc33d6efc0b998fe6396bf92be15 ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: c0386d4d54d2cc33d6efc0b998fe6396bf92be15

Five fixes, for fcsel, fcvtz, fminnm, mls, and non-widening mul.

	sim/aarch64/
	* cpustate.c: Include math.h.
	(aarch64_set_FP_float): Use signbit to check for signed zero.
	(aarch64_set_FP_double): Likewise.
	* simulator.c (do_vec_MOV_immediate, case 0x8): Add missing break.
	(do_vec_mul): In all DO_VEC_WIDENING_MUL calls, make second and fourth
	args same size as third arg.
	(fmaxnm): Use isnan instead of fpclassify.
	(fminnm, dmaxnm, dminnm): Likewise.
	(do_vec_MLS): Reverse order of subtraction operands.
	(dexSimpleFPCondSelect): Call aarch64_get_FP_double or
	aarch64_get_FP_float to get source register contents.
	(UINT_MIN, ULONG_MIN, FLOAT_UINT_MAX, FLOAT_UINT_MIN,
	DOUBLE_UINT_MAX, DOUBLE_UINT_MIN, FLOAT_ULONG_MAX, FLOAT_ULONG_MIN,
	DOUBLE_ULONG_MAX, DOUBLE_ULONG_MIN): New.
	(do_fcvtzu): Use ULONG instead of LONG, and UINT instead of INT in
	raise_exception calls.

	sim/testsuite/sim/aarch64/
	* fcsel.s: New.
	* fcvtz.s: New.
	* fminnm.s: New.
	* mls.s: New.
	* mul.s: New.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Prevent an abort in the FRV disassembler if the target bfd name is unknown.
@ 2017-01-05  9:19 sergiodj+buildbot
  2017-01-07  7:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-05  9:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ae60c3ef45d41b34d40ed5c7b4fdfea289530de ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 0ae60c3ef45d41b34d40ed5c7b4fdfea289530de

Prevent an abort in the FRV disassembler if the target bfd name is unknown.

	PR 20946
	* frv-desc.c (lookup_mach_via_bfd_name): Return NULL if the name
	could not be matched.
	(frv_cgen_cpu_open): Allow for lookup_mach_via_bfd_name returning
	NULL.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix ARI warning
@ 2017-01-05 15:02 sergiodj+buildbot
  2017-01-07 11:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-05 15:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c33cd7f00c7b2d195cdb004559332c397663bae ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1c33cd7f00c7b2d195cdb004559332c397663bae

Fix ARI warning

This patch splits the expression before the && operator instead of
after it.

gdb:

2017-01-05  Yao Qi  <yao.qi@linaro.org>

	* mips-fbsd-tdep.c (mips_fbsd_sigframe_init): Move && to
	new line.
	(mips64_fbsd_sigframe_init): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Update gdb_ptrace.h in HFILES_NO_SRCDIR
@ 2017-01-06 14:17 sergiodj+buildbot
  2017-01-07 15:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 14:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad5cba2adbdb8ec216d44515468bde8d96892c3d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ad5cba2adbdb8ec216d44515468bde8d96892c3d

Update gdb_ptrace.h in HFILES_NO_SRCDIR

Commit e379037 (Move gdb_ptrace.h to nat/), so we should update
file name in HFILES_NO_SRCDIR too.  Otherwise, 'make tags' complains,

$ make tags
make: *** No rule to make target `gdb_ptrace.h', needed by `TAGS'.  Stop.

gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (HFILES_NO_SRCDIR): Replace gdb_ptrace.h
	with nat/gdb_ptrace.h.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Include ax.h in ax-gdb.h
@ 2017-01-06 15:00 sergiodj+buildbot
  2017-01-07 19:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 15:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0b8369c8aa4e05bf8f1b2ce4a79133cf1192a16 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c0b8369c8aa4e05bf8f1b2ce4a79133cf1192a16

Include ax.h in ax-gdb.h

$ make check-headers CHECK_HEADERS="ax-gdb.h"
...

../../binutils-gdb/gdb/ax-gdb.h:104:8: error: 'agent_expr_up' does not name a type
 extern agent_expr_up gen_trace_for_expr (CORE_ADDR, struct expression *,
        ^

gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* ax-gdb.h: Include "ax.h"


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Include break-common.h in nat/aarch64-linux-hw-point.h
@ 2017-01-06 17:58 sergiodj+buildbot
  2017-01-08 11:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc3008c48f17aa67d39e539737a999737cd697a7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: bc3008c48f17aa67d39e539737a999737cd697a7

Include break-common.h in nat/aarch64-linux-hw-point.h

$ make check-headers CHECK_HEADERS="nat/aarch64-linux-hw-point.h"
...
../../binutils-gdb/gdb/nat/aarch64-linux-hw-point.h:169:37: error: use of enum 'target_hw_bp_type' without previous declaration
 int aarch64_handle_breakpoint (enum target_hw_bp_type type, CORE_ADDR addr,
                                     ^
gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* nat/aarch64-linux-hw-point.h: Include break-common.h.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Include serial.h in ser-base.h.
@ 2017-01-06 19:51 sergiodj+buildbot
  2017-01-08 22:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 19:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 44d6d3f93341387bd2c95ea4c941bf99127e7389 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 44d6d3f93341387bd2c95ea4c941bf99127e7389

Include serial.h in ser-base.h.

$ make check-headers CHECK_HEADERS="ser-base.h"
...
../../binutils-gdb/gdb/ser-base.h:33:8: error: 'serial_ttystate' does not name a type
 extern serial_ttystate ser_base_get_tty_state (struct serial *scb);
        ^

gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* ser-base.h: Include serial.h.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Include gdb_proc_service.h in x86-linux-nat.h
@ 2017-01-06 20:40 sergiodj+buildbot
  2017-01-09  2:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 20:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e2d6fa6a38ae2b80a56d786a41d905c9541906f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0e2d6fa6a38ae2b80a56d786a41d905c9541906f

Include gdb_proc_service.h in x86-linux-nat.h

$ make check-headers CHECK_HEADERS="x86-linux-nat.h"
...
../../binutils-gdb/gdb/x86-linux-nat.h:29:8: error: 'ps_err_e' does not name a type
 extern ps_err_e x86_linux_get_thread_area (pid_t pid, void *addr,
        ^

gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* x86-linux-nat.h: Include gdb_proc_service.h.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [D] Fix crash when debug expression enabled.
@ 2017-01-08 10:52 sergiodj+buildbot
  2017-01-09 17:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-08 10:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5e6296e2194add209b546ad49039753a10242f5 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: f5e6296e2194add209b546ad49039753a10242f5

[D] Fix crash when debug expression enabled.

While casting works as expected with expression debugging turned off,
this seems to be an indication that the D language parser function is
doing something wrong in the building of the expression.

Without changing the grammar, using UNOP_CAST_TYPE is the right thing to
do here, as the TypeExp handler has already wrapped the type around a
pair of OP_TYPE opcodes.

gdb/ChangeLog:

	* d-exp.y (CastExpression): Emit UNOP_CAST_TYPE.

gdb/testsuite/ChangeLog:

	* gdb.dlang/debug-expr.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Speed up objdump when displaying disassembly mixed with line number and source code information.
@ 2017-01-09 17:05 sergiodj+buildbot
  2017-01-10  0:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-09 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd6581da62c32a391f9a4c2c5d248a11aa6fa8f7 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: cd6581da62c32a391f9a4c2c5d248a11aa6fa8f7

Speed up objdump when displaying disassembly mixed with line number and source code information.

bfd	* dwarf2.c (lookup_address_in_function_table): Return early if
	there are no functions in the given comp unit, or if the high
	address of the last function in the comp unit is less than the
	desired address.

binutils * objdump.c (display_file): Add new parameter 'last_file'.  If
	last_file is true, do not call bfd_close at the end of the
	function.
	(main): Set the value of the last_file parameter when calling
	display_file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix problems with the implementation of the uzp1 and uzp2 instructions.
@ 2017-01-10  0:02 sergiodj+buildbot
  2017-01-10  7:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-10  0:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a4fb5981b7ec3d4006e93141afb1d0da566bb97b ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: a4fb5981b7ec3d4006e93141afb1d0da566bb97b

Fix problems with the implementation of the uzp1 and uzp2 instructions.

	sim/aarch64/
	* simulator.c (do_vec_UZP): Rewrite.
	sim/testsuite/sim/aarch64/
	* uzp.s: New.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Change return type of ui_out redirect to void
@ 2017-01-10 16:47 sergiodj+buildbot
  2017-01-10 20:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-10 16:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7becfd03bad526c02216eeb5ec2bebae694b1af1 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 7becfd03bad526c02216eeb5ec2bebae694b1af1

Change return type of ui_out redirect to void

All implementations of redirect/do_redirect in the ui_out subsystem
always return 0 (success).  We can therefore clean it up and make them
return void.

gdb/ChangeLog:

	* cli-out.c (cli_ui_out::do_redirect): Change return type to
	void.
	* cli-out.h (cli_ui_out::do_redirect): Likewise.
	* mi/mi-out.c (mi_ui_out::do_redirect): Likewise.
	* mi/mi-out.h (mi_ui_out::do_redirect): Likewise.
	* ui-out.c (ui_out::redirect): Likewise.
	* ui-out.h (ui_out::redirect, ui_out::do_redirect): Likewise.
	* cli/cli-logging.c (set_logging_redirect): Update call site of
	ui_out::redirect.
	(handle_redirections): Likewise.
	* scm-ports.c (ioscm_with_output_to_port_worker): Likewise.
	* top.c (execute_command_to_string): Likewise.
	* utils.c (do_ui_out_redirect_pop): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't use elf_i386_eh_frame_plt directly
@ 2017-01-10 19:51 sergiodj+buildbot
  2017-01-11  1:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-10 19:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f129e49f4d07f4d36319ac757fdcf3a8ce7d605b ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: f129e49f4d07f4d36319ac757fdcf3a8ce7d605b

Don't use elf_i386_eh_frame_plt directly

Use eh_frame_plt_size and eh_frame_plt from elf_i386_plt_layout for
.eh_frame covering the .plt section.

	* elf32-i386.c (elf_i386_size_dynamic_sections): Set
	plt_eh_frame->size to eh_frame_plt_size and use eh_frame_plt.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Change event code to use gdbpy_ref
@ 2017-01-11  7:18 sergiodj+buildbot
  2017-01-11 18:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11  7:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT abf5651e47c0396df58a37951bc03a349169c5f2 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: abf5651e47c0396df58a37951bc03a349169c5f2

Change event code to use gdbpy_ref

This changes the event code in the Python layer to use
gdbpy_ref, simplifying the logic in many places.

It also changes evpy_emit_event not to steal a reference to its
argument.  This is simpler to do now that gdbpy_ref is in use;
it's also a reasonable cleanup in its own right.  While doing this I
realized that evpy_emit_event should not be calling gdbpy_print_stack
(all the outermost callers do this if needed), so I removed this as
well.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-threadevent.c (create_thread_event_object): Use
	gdbpy_ref.
	* python/py-stopevent.c (create_stop_event_object): Simplify.
	(emit_stop_event): Use gdbpy_ref.
	* python/py-signalevent.c (create_signal_event_object): Use
	gdbpy_ref.
	* python/py-newobjfileevent.c (create_new_objfile_event_object)
	(emit_new_objfile_event, create_clear_objfiles_event_object)
	(emit_clear_objfiles_event): Use gdbpy_ref.
	* python/py-infevents.c (create_inferior_call_event_object)
	(create_register_changed_event_object)
	(create_memory_changed_event_object, emit_inferior_call_event)
	(emit_memory_changed_event, emit_register_changed_event): Use
	gdbpy_ref.
	* python/py-exitedevent.c (create_exited_event_object)
	(emit_exited_event): Use gdbpy_ref.
	* python/py-event.h (evpy_emit_event): Remove
	CPYCHECKER_STEALS_REFERENCE_TO_ARG annotation.
	* python/py-event.c (evpy_emit_event): Use gdbpy_ref.
	* python/py-continueevent.c (emit_continue_event): Use
	gdbpy_ref.
	* python/py-breakpoint.c (gdbpy_breakpoint_created)
	(gdbpy_breakpoint_deleted, gdbpy_breakpoint_modified): Use
	gdbpy_ref.
	* python/py-bpevent.c (create_breakpoint_event_object): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use gdbpy_ref in py-framefilter.c
@ 2017-01-11  7:59 sergiodj+buildbot
  2017-01-12 18:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11  7:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee0a3fb85b33b172f704796612c4487ea368d675 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: ee0a3fb85b33b172f704796612c4487ea368d675

Use gdbpy_ref in py-framefilter.c

This changes some code in py-framefilter.c to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-framefilter.c (extract_sym, extract_value)
	(get_py_iter_from_func, bootstrap_python_frame_filters): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use gdbpy_ref in gdbpy_string_to_argv
@ 2017-01-11  8:42 sergiodj+buildbot
  2017-01-12  2:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11  8:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1b3de2e43380a0c51772a40315cd2268573d985 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: d1b3de2e43380a0c51772a40315cd2268573d985

Use gdbpy_ref in gdbpy_string_to_argv

This chanes gdbpy_string_to_argv to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-cmd.c (gdbpy_string_to_argv): Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use gdbpy_ref in call_doc_function
@ 2017-01-11  9:54 sergiodj+buildbot
  2017-01-13  3:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11  9:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1bb44c9f567c75355c1b4417d88cda959e82a3a3 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 1bb44c9f567c75355c1b4417d88cda959e82a3a3

Use gdbpy_ref in call_doc_function

This changes call_doc_function to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-param.c (call_doc_function): Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use gdbpy_ref in py-value.c
@ 2017-01-11 11:14 sergiodj+buildbot
  2017-01-13 14:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 11:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53a0cca3bd0f6ae80b2d6fc34b2873046965c7f0 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 53a0cca3bd0f6ae80b2d6fc34b2873046965c7f0

Use gdbpy_ref in py-value.c

This changes a few functions in py-value.c to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-value.c (value_has_field, get_field_flag)
	(get_field_type, valpy_getitem, convert_value_from_python): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Introduce gdbpy_enter
@ 2017-01-11 11:46 sergiodj+buildbot
  2017-01-13 22:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ecee2c47da3e91c0571683acb5cfb8400402663 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 4ecee2c47da3e91c0571683acb5cfb8400402663

Introduce gdbpy_enter

This introduces gdbpy_enter, a class that can be used to acquire and
release the Python GIL, and also set other Python-related globals used
by gdb.  ensure_python_env is rewritten in terms of this new class.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/python.c (gdbpy_enter): New constructor.
	(~gdbpy_enter): New destructor.
	(restore_python_env, ensure_python_env): Rewrite.
	* python/python-internal.h (gdbpy_enter): New class.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-cmd.c
@ 2017-01-11 12:51 sergiodj+buildbot
  2017-01-14  7:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 12:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ba0cd406511d3edbe643f5e599d79538febedc5 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 6ba0cd406511d3edbe643f5e599d79538febedc5

Use gdbpy_enter in py-cmd.c

Change py-cmd.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-cmd.c (cmdpy_destroyer)
	(cmdpy_completer_handle_brkchars, cmdpy_completer): Use
	gdbpy_enter.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-objfile.c
@ 2017-01-11 14:12 sergiodj+buildbot
  2017-01-14 20:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 14:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d38bcedc2f91692857d257e106dafc9269d8f1a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 2d38bcedc2f91692857d257e106dafc9269d8f1a

Use gdbpy_enter in py-objfile.c

Change py-objfile.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-objfile.c (py_free_objfile): Use gdbpy_enter.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use gdbpy_enter in python.c
@ 2017-01-11 14:43 sergiodj+buildbot
  2017-01-15  3:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 60e600ec691255536ae53e365d0410ecf79bdea2 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 60e600ec691255536ae53e365d0410ecf79bdea2

Use gdbpy_enter in python.c

Change the simple parts of python.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/python.c (gdbpy_eval_from_control_command)
	(gdbpy_source_script, gdbpy_run_events)
	(gdbpy_source_objfile_script, gdbpy_execute_objfile_script)
	(gdbpy_free_type_printers, gdbpy_finish_initialization): Use
	gdbpy_enter.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-xmethod.c
@ 2017-01-11 19:03 sergiodj+buildbot
  2017-01-16 18:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 19:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14b122bf1ce59f5f1b82f6e2a347f4ad89801f45 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 14b122bf1ce59f5f1b82f6e2a347f4ad89801f45

Use gdbpy_enter in py-xmethod.c

This changes the remaining functions in py-xmethod.c to use
gdbpy_enter; using gdbpy_ref and unique_xmalloc_ptr as
appropriate.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-xmethods.c (gdbpy_get_xmethod_result_type): Use
	gdbpy_enter, gdbpy_ref, unique_xmalloc_ptr.
	(gdbpy_invoke_xmethod): Use gdbpy_ref, gdbpy_enter.
	(gdbpy_get_xmethod_arg_types): Use gdbpy_ref,
	unique_xmalloc_ptr.
	(gdbpy_get_xmethod_arg_types): Use gdbpy_ref, gdbpy_enter.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-finishbreakpoint.c
@ 2017-01-11 19:07 sergiodj+buildbot
  2017-01-14 11:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e7c365ee0ea2551f9f840b71081fdf759088b5e ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 6e7c365ee0ea2551f9f840b71081fdf759088b5e

Use gdbpy_enter in py-finishbreakpoint.c

Change py-finishbreakpoint.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-finishbreakpoint.c (bpfinishpy_handle_stop)
	(bpfinishpy_handle_exit): Use gdbpy_enter.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use gdbpy_ref in invoke_match_method
@ 2017-01-12  5:21 sergiodj+buildbot
  2017-01-16 14:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-12  5:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf1ca3b9476185fb6e301d85e646f5d2af95e257 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: bf1ca3b9476185fb6e301d85e646f5d2af95e257

Use gdbpy_ref in invoke_match_method

Change invoke_match_method to use gdbpy_ref.
I neglected to convert this function in my earlier series.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-xmethods.c (invoke_match_method): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix unused-but-set warning in elf32-cris.c:elf_cris_finish_dynamic_symbol
@ 2017-01-27  8:31 sergiodj+buildbot
  2017-01-27 15:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-27  8:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22d9a0dee3a69973858000b326cf8eaa14ce7180 ***

Author: Hans-Peter Nilsson <hp@bitrange.com>
Branch: master
Commit: 22d9a0dee3a69973858000b326cf8eaa14ce7180

Fix unused-but-set warning in elf32-cris.c:elf_cris_finish_dynamic_symbol

	* elf32-cris.c (elf_cris_finish_dynamic_symbol): Remove now unused
	local variable dynobj.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbserver-amd64: add HAVE_STRUCT_USER_REGS_STRUCT_(GS|FS)_BASE for gdbserver.
@ 2017-01-27 14:35 sergiodj+buildbot
  2017-01-28  4:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-27 14:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 239b6d10954b18ce089e9c3a667e7f2df3655476 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 239b6d10954b18ce089e9c3a667e7f2df3655476

gdbserver-amd64: add HAVE_STRUCT_USER_REGS_STRUCT_(GS|FS)_BASE for gdbserver.

The macros mentioned in the title were set only for GDB. In gdbserver they
were not set until now.  To align the code in GDB and gdbserver these macros
are also added into gdbserver, enabling read and write of gs_base and fs_base
registers from the system in new and old kernels.

2017-01-27  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/gdbserver/ChangeLog:

    	* configure.ac: Check if the fs_base and gs_base members of
    	`struct user_regs_struct' exist.
    	* config.in: Regenerated.
    	* configure: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] amd64: remove additional comparison for validity of a register number.
@ 2017-01-27 15:16 sergiodj+buildbot
  2017-01-28  8:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-27 15:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7005d26ac72abbf12e02947ab87dbb3804f326a8 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 7005d26ac72abbf12e02947ab87dbb3804f326a8

amd64: remove additional comparison for validity of a register number.

Second part of the && is already guaranteed in the "regnum < num_regs"
due to comparison above.

2017-01-27  Walfred Tedeschi  <walfred.tedeschi@intel.com>

	* amd64-nat.c (amd64_native_gregset_reg_offset): Simplify logic
	that checks validity of a register number.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] amd64-linux: expose system register FS_BASE and GS_BASE for Linux.
@ 2017-01-27 16:49 sergiodj+buildbot
  2017-01-28 16:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-27 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2735833d5fb220983d09770087b573fed5bf93cd ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 2735833d5fb220983d09770087b573fed5bf93cd

amd64-linux: expose system register FS_BASE and GS_BASE for Linux.

This patch allows examination of the registers FS_BASE and GS_BASE
for Linux Systems running on 64bit. Tests for simple read and write
of the new registers is also added with this patch.

2017-01-27  Walfred Tedeschi  <walfred.tedeschi@intel.com>
	    Richard Henderson  <rth@redhat.com>

gdb/ChangeLog:

	* amd64-linux-nat.c (PTRACE_ARCH_PRCTL): New define.
	(amd64_linux_fetch_inferior_registers): Add case to fetch FS_BASE
	GS_BASE for older kernels.
	(amd64_linux_store_inferior_registers): Add case to store FS_BASE
	GS_BASE for older kernels.
	* amd64-linux-tdep.c (amd64_linux_gregset_reg_offset): Add FS_BASE
	and GS_BASE to the offset table.
	(amd64_linux_register_reggroup_p): Add FS_BASE and GS_BASE to the
	system register group.
	* amd64-nat.c (amd64_native_gregset_reg_offset): Implements case
	for older kernels.
	* amd64-tdep.c (amd64_init_abi): Add segment registers for the
	amd64 ABI.
	* amd64-tdep.h (amd64_regnum): Add AMD64_FSBASE_REGNUM and
	AMD64_GSBASE_REGNUM.
	(AMD64_NUM_REGS): Set to AMD64_GSBASE_REGNUM + 1.
	* features/Makefile (amd64-linux.dat, amd64-avx-linux.dat)
	(amd64-mpx-linux.dat, amd64-avx512-linux.dat, x32-linux.dat)
	(x32-avx-linux.dat, x32-avx512-linux.dat): Add
	i386/64bit-segments.xml in those rules.
	* features/i386/64bit-segments.xml: New file.
	* features/i386/amd64-avx-mpx-linux.xml: Add 64bit-segments.xml.
	* features/i386/amd64-avx-linux.xml: Add 64bit-segments.xml.
	* features/i386/amd64-avx512-linux.xml: Add 64bit-segments.xml.
	* features/i386/amd64-mpx-linux.xml: Add 64bit-segments.xml.
	* features/i386/x32-avx512-linux.xml: Add 64bit-segments.xml.
	* features/i386/x32-avx-linux.xml: Add 64bit-segments.xml.
	* features/i386/amd64-linux.xml: Add 64bit-segments.xml.
	* features/i386/amd64-avx-linux.c: Regenerated.
	* features/i386/amd64-avx-mpx-linux.c: Regenerated.
	* features/i386/amd64-avx-mpx.c: Regenerated.
	* features/i386/amd64-avx512-linux.c: Regenerated.
	* features/i386/amd64-linux.c: Regenerated.
	* features/i386/amd64-mpx-linux.c: Regenerated.
	* features/i386/i386-avx-mpx-linux.c: Regenerated.
	* features/i386/i386-avx-mpx.c: Regenerated.
	* features/i386/x32-avx-linux.c: Regenerated.
	* features/i386/x32-avx512-linux.c: Regenerated.
	* regformats/i386/amd64-avx-linux.dat: Regenerated.
	* regformats/i386/amd64-avx-mpx-linux.dat: Regenerated.
	* regformats/i386/amd64-avx512-linux.dat: Regenerated.
	* regformats/i386/amd64-linux.dat: Regenerated.
	* regformats/i386/amd64-mpx-linux.dat: Regenerated.
	* regformats/i386/x32-avx-linux.dat: Regenerated.
	* regformats/i386/x32-avx512-linux.dat: Regenerated.
	* regformats/i386/x32-linux.dat: Regenerated.

gdb/doc/ChangeLog:

	* gdb.texinfo (i386 Features): Add system segment registers
	as feature.

gdb/gdbserver/ChangeLog:

	* linux-x86-low.c (x86_64_regmap): Add fs_base and gs_base
	to the register table.
	(x86_fill_gregset): Add support for old kernels for the
	fs_base and gs_base system registers.
	(x86_store_gregset): Likewise.
	* configure.srv (srv_i386_64bit_xmlfiles): Add 64bit-segments.xml.

gdb/testsuite/ChangeLog:

	* gdb.arch/amd64-gs_base.c: New file.
	* gdb.arch/amd64-gs_base.exp: New file.

Change-Id: I2e0eeb93058a2320d4d3b045082643cfe4aff963
Signed-off-by: Walfred Tedeschi <walfred.tedeschi@intel.com>


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: make_scoped_restore and types convertible to T
@ 2017-01-31 23:53 sergiodj+buildbot
  2017-02-01  1:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-01-31 23:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 60adb36c08942fd4a2f8bf598864254c043668a1 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 60adb36c08942fd4a2f8bf598864254c043668a1

gdb: make_scoped_restore and types convertible to T

A following patch will want to do

   string_file str_file;

   scoped_restore save_stdout
    = make_scoped_restore (&gdb_stdout, &str_file);

where gdb_stdout is a ui_file *, and string_file is a type that
inherits from ui_file, but that doesn't compile today:

  src/gdb/top.c: In function std::__cxx11::string execute_command_to_string(char*, int):
  src/gdb/top.c:710:50: error: no matching function for call to make_scoped_restore(ui_file**, string_file*)
       = make_scoped_restore (&gdb_stdout, &str_file);
						    ^
  [...]
  In file included from src/gdb/utils.h:25:0,
		   from src/gdb/defs.h:732,
		   from src/gdb/top.c:20:
  src/gdb/common/scoped_restore.h:94:24: note: candidate: template<class T> scoped_restore_tmpl<T> make_scoped_restore(T*, T)
   scoped_restore_tmpl<T> make_scoped_restore (T *var, T value)
			  ^
  src/gdb/common/scoped_restore.h:94:24: note:   template argument deduction/substitution failed:
  src/gdb/top.c:710:50: note:   deduced conflicting types for parameter T (ui_file* and string_file*)
       = make_scoped_restore (&gdb_stdout, &str_file);
						    ^

This commit makes code such as the above possible.

gdb/ChangeLog:
2017-01-31  Pedro Alves  <palves@redhat.com>

	* common/scoped_restore.h
	(scoped_restore_tmpl::scoped_restore_tmpl): Template on T2, and
	change the value's parameter type to T2.
	(make_scoped_restore): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb/varobj.c: Fix leak
@ 2017-02-01  0:40 sergiodj+buildbot
  2017-02-01  6:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-01  0:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b47413b47e103677fedb7cd1301c62fee01ac4ba ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b47413b47e103677fedb7cd1301c62fee01ac4ba

gdb/varobj.c: Fix leak

Whoops, this function returns a std::string.

gdb/ChangeLog:
2017-01-31  Pedro Alves  <palves@redhat.com>

	* varobj.c (varobj_value_get_print_value): Remove xstrdup call.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] thread: add can_access_registers_ptid
@ 2017-02-01 13:56 sergiodj+buildbot
  2017-02-01 21:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-01 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf77c34ea71c27c3cb6dd31c9448249276e8a8a6 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: cf77c34ea71c27c3cb6dd31c9448249276e8a8a6

thread: add can_access_registers_ptid

Add a function can_access_registers_ptid that behaves like
validate_registers_access but returns a boolean value instead of throwing an
exception.

gdb/
	* gdbthread.h (can_access_registers_ptid): New.
	* thread.c (can_access_registers_ptid): New.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] btrace: add unsupported/untested messages when skipping tests
@ 2017-02-01 15:06 sergiodj+buildbot
  2017-02-02  6:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-01 15:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5ac99b0828d4e1dfa33540b428c0fc6c32eda67 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: b5ac99b0828d4e1dfa33540b428c0fc6c32eda67

btrace: add unsupported/untested messages when skipping tests

We may silently skip gdb.btrace tests if

  - the target does not support record-btrace
  - the target does not support TSX
  - the target does not support gdbserver
  - we fail to compile the test
  - we fail to run to main

Add unsupported/untested messages for each of those.

testsuite/
	* gdb.btrace/buffer-size.exp: Add unsupported/untested message if
	the test is skipped.
	* gdb.btrace/data.exp: Likewise.
	* gdb.btrace/delta.exp: Likewise.
	* gdb.btrace/dlopen.exp: Likewise.
	* gdb.btrace/enable-running.exp: Likewise.
	* gdb.btrace/enable.exp: Likewise.
	* gdb.btrace/exception.exp: Likewise.
	* gdb.btrace/function_call_history.exp: Likewise.
	* gdb.btrace/gcore.exp: Likewise.
	* gdb.btrace/instruction_history.exp: Likewise.
	* gdb.btrace/multi-thread-step.exp: Likewise.
	* gdb.btrace/nohist.exp: Likewise.
	* gdb.btrace/non-stop.exp: Likewise.
	* gdb.btrace/reconnect.exp: Likewise.
	* gdb.btrace/record_goto-step.exp: Likewise.
	* gdb.btrace/record_goto.exp: Likewise.
	* gdb.btrace/rn-dl-bind.exp: Likewise.
	* gdb.btrace/segv.exp: Likewise.
	* gdb.btrace/step.exp: Likewise.
	* gdb.btrace/stepi.exp: Likewise.
	* gdb.btrace/tailcall-only.exp: Likewise.
	* gdb.btrace/tailcall.exp: Likewise.
	* gdb.btrace/tsx.exp: Likewise.
	* gdb.btrace/unknown_functions.exp: Likewise.
	* gdb.btrace/vdso.exp: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] btrace, testsuite: fix extended-remote non-stop test
@ 2017-02-01 15:42 sergiodj+buildbot
  2017-02-02 10:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-01 15:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a1c7e2881226bb9734d7c31c9415c636f35921d ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 0a1c7e2881226bb9734d7c31c9415c636f35921d

btrace, testsuite: fix extended-remote non-stop test

With --target_board=native-extended-gdbserver non-stop tests are failing with

    UNTESTED: gdb.btrace/non-stop.exp: failed to run to main

Fix that by adding '-ex "set non-stop on"' to GDBFLAGS before restarting.

testsuite/
	* gdb.btrace/non-stop.exp: Add '-ex "set non-stop on"' to GDBFLAGS.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Big-endian targets: Don't ignore offset into DW_OP_implicit_value
@ 2017-02-01 16:25 sergiodj+buildbot
  2017-02-02 22:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-01 16:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7346ef59bb33e28161d78ab478c3476b3dab2e8e ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 7346ef59bb33e28161d78ab478c3476b3dab2e8e

Big-endian targets: Don't ignore offset into DW_OP_implicit_value

When a variable's location is expressed as DW_OP_implicit_value, but the
given value is longer than needed, which bytes should be used?  GDB's
current logic was introduced with a patch from 2011 and uses the "least
significant" bytes:

  https://sourceware.org/ml/gdb-patches/2011-08/msg00123.html

Now consider a sub-value from such a location at a given offset, accessed
through DW_OP_implicit_pointer.  Which bytes should be used for that?  The
patch above *always* uses the last bytes on big-endian targets, ignoring
the offset.

E.g., given the code snippet

  const char foo[] = "Hello, world!";
  const char *a = &foo[0];
  const char *b = &foo[7];

assume that `foo' is described as DW_OP_implicit_value and `a' and `b'
each as DW_OP_implicit_pointer into that value.  Then with current GDB
`*a' and `*b' yield the same result -- the string's zero terminator.

This patch basically reverts the portion of the patch above that deals
with DW_OP_implicit_value.  This fixes the offset handling and also goes
back to dropping the last instead of the first bytes on big-endian targets
if the implicit value is longer than needed.  The latter aspect of the
change probably doesn't matter for actual programs, but simplifies the
logic.

The patch also cleans up the original code a bit and adds appropriate test
cases.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/dw2-op-stack-value.exp: Adjust expected result of
	taking a 2-byte value out of a 4-byte DWARF implicit value on
	big-endian targets.
	* gdb.dwarf2/nonvar-access.exp: Add more comments to existing
	logic.  Add test cases for DW_OP_implicit.

gdb/ChangeLog:

	* dwarf2loc.c (dwarf2_evaluate_loc_desc_full): For
	DWARF_VALUE_LITERAL, no longer ignore the offset on big-endian
	targets.  And if the implicit value is longer than needed, extract
	the first bytes instead of the "least significant" ones.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy
@ 2017-02-02 12:25 sergiodj+buildbot
  2017-02-03  9:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-02 12:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d7e747318f4d04af033f16325f9b6d74f67079ec ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d7e747318f4d04af033f16325f9b6d74f67079ec

Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy

This patch starts from the desire to eliminate
make_cleanup_ui_file_delete, but then goes beyond.  It makes ui_file &
friends a real C++ class hierarchy, and switches temporary
ui_file-like objects to stack-based allocation.

- mem_fileopen -> string_file

mem_fileopen is replaced with a new string_file class that is treated
as a value class created on the stack.  This alone eliminates most
make_cleanup_ui_file_delete calls, and, simplifies code a whole lot
(diffstat shows around 1k loc dropped.)

string_file's internal buffer is a std::string, thus the "string" in
the name.  This simplifies the implementation much, compared to
mem_fileopen, which managed growing its internal buffer manually.

- ui_file_as_string, ui_file_strdup, ui_file_obsavestring all gone

The new string_file class has a string() method that provides direct
writable access to the internal std::string buffer.  This replaced
ui_file_as_string, which forced a copy of the same data the stream had
inside.  With direct access via a writable reference, we can instead
move the string out of the string_stream, avoiding deep string
copying.

Related, ui_file_xstrdup calls are replaced with xstrdup'ping the
stream's string, and ui_file_obsavestring is replaced by
obstack_copy0.

With all those out of the way, getting rid of the weird ui_file_put
mechanism was possible.

- New ui_file::printf, ui_file::puts, etc. methods

These simplify / clarify client code.  I considered splitting
client-code changes, like these, e.g.:

  -  stb = mem_fileopen ();
  -  fprintf_unfiltered (stb, "%s%s%s",
  -		      _("The valid values are:\n"),
  -		      regdesc,
  -		      _("The default is \"std\"."));
  +  string_file stb;
  +  stb.printf ("%s%s%s",
  +	      _("The valid values are:\n"),
  +	      regdesc,
  +	      _("The default is \"std\"."));

In two steps, with the first step leaving fprintf_unfiltered (etc.)
calls in place, and only afterwards do a pass to change all those to
call stb.printf etc..  I didn't do that split, because (when I tried),
it turned out to be pointless make-work: the first pass would have to
touch the fprintf_unfiltered line anyway, to replace "stb" with
"&stb".

- gdb_fopen replaced with stack-based objects

This avoids the need for cleanups or unique_ptr's.  I.e., this:

      struct ui_file *file = gdb_fopen (filename, "w");
      if (filename == NULL)
 	perror_with_name (filename);
      cleanups = make_cleanup_ui_file_delete (file);
      // use file.
      do_cleanups (cleanups);

is replaced with this:

      stdio_file file;
      if (!file.open (filename, "w"))
 	perror_with_name (filename);
      // use file.

- odd contorsions in null_file_write / null_file_fputs around when to
  call to_fputs / to_write eliminated.

- Global null_stream object

A few places that were allocating a ui_file in order to print to
"nowhere" are adjusted to instead refer to a new 'null_stream' global
stream.

- TUI's tui_sfileopen eliminated.  TUI's ui_file much simplified

The TUI's ui_file was serving a dual purpose.  It supported being used
as string buffer, and supported being backed by a stdio FILE.  The
string buffer part is gone, replaced by using of string_file.  The
'FILE *' support is now much simplified, by making the TUI's ui_file
inherit from stdio_file.

gdb/ChangeLog:
2017-02-02  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (type_as_string): Use string_file.
	* ada-valprint.c (ada_print_floating): Use string_file.
	* ada-varobj.c (ada_varobj_scalar_image)
	(ada_varobj_get_value_image): Use string_file.
	* aix-thread.c (aix_thread_extra_thread_info): Use string_file.
	* arm-tdep.c (_initialize_arm_tdep): Use string_printf.
	* breakpoint.c (update_inserted_breakpoint_locations)
	(insert_breakpoint_locations, reattach_breakpoints)
	(print_breakpoint_location, print_one_detail_ranged_breakpoint)
	(print_it_watchpoint): Use string_file.
	(save_breakpoints): Use stdio_file.
	* c-exp.y (oper): Use string_file.
	* cli/cli-logging.c (set_logging_redirect): Use ui_file_up and
	tee_file.
	(pop_output_files): Use delete.
	(handle_redirections): Use stdio_file and tee_file.
	* cli/cli-setshow.c (do_show_command): Use string_file.
	* compile/compile-c-support.c (c_compute_program): Use
	string_file.
	* compile/compile-c-symbols.c (generate_vla_size): Take a
	'string_file &' instead of a 'ui_file *'.
	(generate_c_for_for_one_variable): Take a 'string_file &' instead
	of a 'ui_file *'.  Use string_file.
	(generate_c_for_variable_locations): Take a 'string_file &'
	instead of a 'ui_file *'.
	* compile/compile-internal.h (generate_c_for_for_one_variable):
	Take a 'string_file &' instead of a 'ui_file *'.
	* compile/compile-loc2c.c (push, pushf, unary, binary)
	(print_label, pushf_register_address, pushf_register)
	(do_compile_dwarf_expr_to_c): Take a 'string_file &' instead of a
	'ui_file *'.  Adjust.
	* compile/compile.c (compile_to_object): Use string_file.
	* compile/compile.h (compile_dwarf_expr_to_c)
	(compile_dwarf_bounds_to_c): Take a 'string_file &' instead of a
	'ui_file *'.
	* cp-support.c (inspect_type): Use string_file and obstack_copy0.
	(replace_typedefs_qualified_name): Use string_file and
	obstack_copy0.
	* disasm.c (gdb_pretty_print_insn): Use string_file.
	(gdb_disassembly): Adjust reference the null_stream global.
	(do_ui_file_delete): Delete.
	(gdb_insn_length): Use null_stream.
	* dummy-frame.c (maintenance_print_dummy_frames): Use stdio_file.
	* dwarf2loc.c (dwarf2_compile_property_to_c)
	(locexpr_generate_c_location, loclist_generate_c_location): Take a
	'string_file &' instead of a 'ui_file *'.
	* dwarf2loc.h (dwarf2_compile_property_to_c): Likewise.
	* dwarf2read.c (do_ui_file_peek_last): Delete.
	(dwarf2_compute_name): Use string_file.
	* event-top.c (gdb_setup_readline): Use stdio_file.
	* gdbarch.sh (verify_gdbarch): Use string_file.
	* gdbtypes.c (safe_parse_type): Use null_stream.
	* guile/scm-breakpoint.c (gdbscm_breakpoint_commands): Use
	string_file.
	* guile/scm-disasm.c (gdbscm_print_insn_from_port): Take a
	'string_file *' instead of a 'ui_file *'.
	(gdbscm_arch_disassemble): Use string_file.
	* guile/scm-frame.c (frscm_print_frame_smob): Use string_file.
	* guile/scm-ports.c (class ioscm_file_port): Now a class that
	inherits from ui_file.
	(ioscm_file_port_delete, ioscm_file_port_rewind)
	(ioscm_file_port_put): Delete.
	(ioscm_file_port_write): Rename to ...
	(ioscm_file_port::write): ... this.  Remove file_port_magic
	checks.
	(ioscm_file_port_new): Delete.
	(ioscm_with_output_to_port_worker): Use ioscm_file_port and
	ui_file_up.
	* guile/scm-type.c (tyscm_type_name): Use string_file.
	* guile/scm-value.c (vlscm_print_value_smob, gdbscm_value_print):
	Use string_file.
	* infcmd.c (print_return_value_1): Use string_file.
	* infrun.c (print_target_wait_results): Use string_file.
	* language.c (add_language): Use string_file.
	* location.c (explicit_to_string_internal): Use string_file.
	* main.c (captured_main_1): Use null_file.
	* maint.c (maintenance_print_architecture): Use stdio_file.
	* mi/mi-cmd-stack.c (list_arg_or_local): Use string_file.
	* mi/mi-common.h (struct mi_interp) <out, err, log, targ,
	event_channel>: Change type to mi_console_file pointer.
	* mi/mi-console.c (mi_console_file_fputs, mi_console_file_flush)
	(mi_console_file_delete): Delete.
	(struct mi_console_file): Delete.
	(mi_console_file_magic): Delete.
	(mi_console_file_new): Delete.
	(mi_console_file::mi_console_file): New.
	(mi_console_file_delete): Delete.
	(mi_console_file_fputs): Delete.
	(mi_console_file::write): New.
	(mi_console_raw_packet): Delete.
	(mi_console_file::flush): New.
	(mi_console_file_flush): Delete.
	(mi_console_set_raw): Rename to ...
	(mi_console_file::set_raw): ... this.
	* mi/mi-console.h (class mi_console_file): New class.
	(mi_console_file_new, mi_console_set_raw): Delete.
	* mi/mi-interp.c (mi_interpreter_init): Use mi_console_file.
	(mi_set_logging): Use delete and tee_file.  Adjust.
	* mi/mi-main.c (output_register): Use string_file.
	(mi_cmd_data_evaluate_expression): Use string_file.
	(mi_cmd_data_read_memory): Use string_file.
	(mi_cmd_execute, print_variable_or_computed): Use string_file.
	* mi/mi-out.c (mi_ui_out::main_stream): New.
	(mi_ui_out::rewind): Use main_stream and
	string_file.
	(mi_ui_out::put): Use main_stream and string_file.
	(mi_ui_out::mi_ui_out): Remove 'stream' parameter.
	Allocate a 'string_file' instead.
	(mi_out_new): Don't allocate a mem_fileopen stream here.
	* mi/mi-out.h (mi_ui_out::mi_ui_out): Remove 'stream' parameter.
	(mi_ui_out::main_stream): Declare method.
	* printcmd.c (eval_command): Use string_file.
	* psymtab.c (maintenance_print_psymbols): Use stdio_file.
	* python/py-arch.c (archpy_disassemble): Use string_file.
	* python/py-breakpoint.c (bppy_get_commands): Use string_file.
	* python/py-frame.c (frapy_str): Use string_file.
	* python/py-framefilter.c (py_print_type, py_print_single_arg):
	Use string_file.
	* python/py-type.c (typy_str): Use string_file.
	* python/py-unwind.c (unwind_infopy_str): Use string_file.
	* python/py-value.c (valpy_str): Use string_file.
	* record-btrace.c (btrace_insn_history): Use string_file.
	* regcache.c (regcache_print): Use stdio_file.
	* reggroups.c (maintenance_print_reggroups): Use stdio_file.
	* remote.c (escape_buffer): Use string_file.
	* rust-lang.c (rust_get_disr_info): Use string_file.
	* serial.c (serial_open_ops_1): Use stdio_file.
	(do_serial_close): Use delete.
	* stack.c (print_frame_arg): Use string_file.
	(print_frame_args): Remove local mem_fileopen stream, not used.
	(print_frame): Use string_file.
	* symmisc.c (maintenance_print_symbols): Use stdio_file.
	* symtab.h (struct symbol_computed_ops) <generate_c_location>:
	Take a 'string_file *' instead of a 'ui_file *'.
	* top.c (new_ui): Use stdio_file and stderr_file.
	(free_ui): Use delete.
	(execute_command_to_string): Use string_file.
	(quit_confirm): Use string_file.
	* tracepoint.c (collection_list::append_exp): Use string_file.
	* tui/tui-disasm.c (tui_disassemble): Use string_file.
	* tui/tui-file.c: Don't include "ui-file.h".
	(enum streamtype, struct tui_stream): Delete.
	(tui_file_new, tui_file_delete, tui_fileopen, tui_sfileopen)
	(tui_file_isatty, tui_file_rewind, tui_file_put): Delete.
	(tui_file::tui_file): New method.
	(tui_file_fputs): Delete.
	(tui_file_get_strbuf): Delete.
	(tui_file::puts): New method.
	(tui_file_adjust_strbuf): Delete.
	(tui_file_flush): Delete.
	(tui_file::flush): New method.
	* tui/tui-file.h: Tweak intro comment.
	Include ui-file.h.
	(tui_fileopen, tui_sfileopen, tui_file_get_strbuf)
	(tui_file_adjust_strbuf): Delete declarations.
	(class tui_file): New class.
	* tui/tui-io.c (tui_initialize_io): Use tui_file.
	* tui/tui-regs.c (tui_restore_gdbout): Use delete.
	(tui_register_format): Use string_stream.
	* tui/tui-stack.c (tui_make_status_line): Use string_file.
	(tui_get_function_from_frame): Use string_file.
	* typeprint.c (type_to_string): Use string_file.
	* ui-file.c (struct ui_file, ui_file_magic, ui_file_new): Delete.
	(null_stream): New global.
	(ui_file_delete): Delete.
	(ui_file::ui_file): New.
	(null_file_isatty): Delete.
	(ui_file::~ui_file): New.
	(null_file_rewind): Delete.
	(ui_file::printf): New.
	(null_file_put): Delete.
	(null_file_flush): Delete.
	(ui_file::putstr): New.
	(null_file_write): Delete.
	(ui_file::putstrn): New.
	(null_file_read): Delete.
	(ui_file::putc): New.
	(null_file_fputs): Delete.
	(null_file_write_async_safe): Delete.
	(ui_file::vprintf): New.
	(null_file_delete): Delete.
	(null_file::write): New.
	(null_file_fseek): Delete.
	(null_file::puts): New.
	(ui_file_data): Delete.
	(null_file::write_async_safe): New.
	(gdb_flush, ui_file_isatty): Adjust.
	(ui_file_put, ui_file_rewind): Delete.
	(ui_file_write): Adjust.
	(ui_file_write_for_put): Delete.
	(ui_file_write_async_safe, ui_file_read): Adjust.
	(ui_file_fseek): Delete.
	(fputs_unfiltered): Adjust.
	(set_ui_file_flush, set_ui_file_isatty, set_ui_file_rewind)
	(set_ui_file_put, set_ui_file_write, set_ui_file_write_async_safe)
	(set_ui_file_read, set_ui_file_fputs, set_ui_file_fseek)
	(set_ui_file_data): Delete.
	(string_file::~string_file, string_file::write)
	(struct accumulated_ui_file, do_ui_file_xstrdup, ui_file_xstrdup)
	(do_ui_file_as_string, ui_file_as_string): Delete.
	(do_ui_file_obsavestring, ui_file_obsavestring): Delete.
	(struct mem_file): Delete.
	(mem_file_new): Delete.
	(stdio_file::stdio_file): New.
	(mem_file_delete): Delete.
	(stdio_file::stdio_file): New.
	(mem_fileopen): Delete.
	(stdio_file::~stdio_file): New.
	(mem_file_rewind): Delete.
	(stdio_file::set_stream): New.
	(mem_file_put): Delete.
	(stdio_file::open): New.
	(mem_file_write): Delete.
	(stdio_file_magic, struct stdio_file): Delete.
	(stdio_file_new, stdio_file_delete, stdio_file_flush): Delete.
	(stdio_file::flush): New.
	(stdio_file_read): Rename to ...
	(stdio_file::read): ... this.  Adjust.
	(stdio_file_write): Rename to ...
	(stdio_file::write): ... this.  Adjust.
	(stdio_file_write_async_safe): Rename to ...
	(stdio_file::write_async_safe) ... this.  Adjust.
	(stdio_file_fputs): Rename to ...
	(stdio_file::puts) ... this.  Adjust.
	(stdio_file_isatty): Delete.
	(stdio_file_fseek): Delete.
	(stdio_file::isatty): New.
	(stderr_file_write): Rename to ...
	(stderr_file::write) ... this.  Adjust.
	(stderr_file_fputs): Rename to ...
	(stderr_file::puts) ... this.  Adjust.
	(stderr_fileopen, stdio_fileopen, gdb_fopen): Delete.
	(stderr_file::stderr_file): New.
	(tee_file_magic): Delete.
	(struct tee_file): Delete.
	(tee_file::tee_file): New.
	(tee_file_new): Delete.
	(tee_file::~tee_file): New.
	(tee_file_delete): Delete.
	(tee_file_flush): Rename to ...
	(tee_file::flush): ... this.  Adjust.
	(tee_file_write): Rename to ...
	(tee_file::write): ... this.  Adjust.
	(tee_file::write_async_safe): New.
	(tee_file_fputs): Rename to ...
	(tee_file::puts): ... this.  Adjust.
	(tee_file_isatty): Rename to ...
	(tee_file::isatty): ... this.  Adjust.
	* ui-file.h (struct obstack, struct ui_file): Don't
	forward-declare.
	(ui_file_new, ui_file_flush_ftype, set_ui_file_flush)
	(ui_file_write_ftype)
	(set_ui_file_write, ui_file_fputs_ftype, set_ui_file_fputs)
	(ui_file_write_async_safe_ftype, set_ui_file_write_async_safe)
	(ui_file_read_ftype, set_ui_file_read, ui_file_isatty_ftype)
	(set_ui_file_isatty, ui_file_rewind_ftype, set_ui_file_rewind)
	(ui_file_put_method_ftype, ui_file_put_ftype, set_ui_file_put)
	(ui_file_delete_ftype, set_ui_file_data, ui_file_fseek_ftype)
	(set_ui_file_fseek): Delete.
	(ui_file_data, ui_file_delete, ui_file_rewind)
	(struct ui_file): New.
	(ui_file_up): New.
	(class null_file): New.
	(null_stream): Declare.
	(ui_file_write_for_put, ui_file_put): Delete.
	(ui_file_xstrdup, ui_file_as_string, ui_file_obsavestring):
	Delete.
	(ui_file_fseek, mem_fileopen, stdio_fileopen, stderr_fileopen)
	(gdb_fopen, tee_file_new): Delete.
	(struct string_file): New.
	(struct stdio_file): New.
	(stdio_file_up): New.
	(struct stderr_file): New.
	(class tee_file): New.
	* ui-out.c (ui_out::field_stream): Take a 'string_file &' instead
	of a 'ui_file *'.  Adjust.
	* ui-out.h (class ui_out) <field_stream>: Likewise.
	* utils.c (do_ui_file_delete, make_cleanup_ui_file_delete)
	(null_stream): Delete.
	(error_stream): Take a 'string_file &' instead of a 'ui_file *'.
	Adjust.
	* utils.h (struct ui_file): Delete forward declaration..
	(make_cleanup_ui_file_delete, null_stream): Delete declarations.
	(error_stream): Take a 'string_file &' instead of a
	'ui_file *'.
	* varobj.c (varobj_value_get_print_value): Use string_file.
	* xtensa-tdep.c (xtensa_verify_config): Use string_file.
	* gdbarch.c: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Tweak pretty_print_disassembler's intro comment
@ 2017-02-02 13:57 sergiodj+buildbot
  2017-02-03 17:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-02 13:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c99cc448c805b6bd481603155078881a503cd64a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c99cc448c805b6bd481603155078881a503cd64a

Tweak pretty_print_disassembler's intro comment

gdb/ChangeLog:
2017-02-02  Pedro Alves  <palves@redhat.com>

	* disasm.h (gdb_pretty_print_disassembler): Tweak intro comment.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix "-gdb-set logging redirect on" crash
@ 2017-02-02 14:53 sergiodj+buildbot
  2017-02-03 21:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-02 14:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5be5dbf0ce3d2eb20003fea3691eaa6bfa5710d2 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5be5dbf0ce3d2eb20003fea3691eaa6bfa5710d2

Fix "-gdb-set logging redirect on" crash

This commit fixes a "-gdb-set logging redirect on" crash by not
handling "logging redirect on" on the fly.

Previous discussion here:
 https://sourceware.org/ml/gdb-patches/2017-01/msg00467.html

Code for handling "logging redirect on" on the fly was added here:
 https://sourceware.org/ml/gdb-patches/2010-08/msg00202.html

Meanwhile, MI gained support for logging, but flipping redirect "on"
on the fly was not considered.  The result is that this sequence of
commands crashes GDB:

 -gdb-set logging on
 -gdb-set logging redirect on

 Program received signal SIGSEGV, Segmentation fault.
 0x00000000008dd7bc in gdb_flush (file=0x2a097f0) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/ui-file.c:95
 194       file->to_flush (file);
 (top-gdb) bt
 #0  0x00000000008dd7bc in gdb_flush(ui_file*) (file=0x2a097f0) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/ui-file.c:95
 #1  0x00000000007b5f34 in gdb_wait_for_event(int) (block=0) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/event-loop.c:752
 #2  0x00000000007b52b6 in gdb_do_one_event() () at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/event-loop.c:322
 #3  0x00000000007b5362 in start_event_loop() () at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/event-loop.c:371
 #4  0x000000000082704a in captured_command_loop(void*) (data=0x0) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/main.c:325
 #5  0x00000000007b8d7c in catch_errors(int (*)(void*), void*, char*, return_mask) (func=0x827008 <captured_command_loop(void*)>, func_args=0x0, errstring=0x11dee51 "", mask=RETURN_MASK_ALL) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/exceptions.c:236
 #6  0x000000000082839b in captured_main(void*) (data=0x7fffffffd820) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/main.c:1148
 During symbol reading, cannot get low and high bounds for subprogram DIE at 24065.
 #7  0x00000000008283c4 in gdb_main(captured_main_args*) (args=0x7fffffffd820) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/main.c:1158
 #8  0x0000000000412d4d in main(int, char**) (argc=4, argv=0x7fffffffd928) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/gdb.c:32

The handling of redirect on the fly is not really a use case we need
to handle, IMO.  Its inconsistent (other "set logging foo" commands
aren't handled on the fly), and complicates the code significantly.
Instead of complicating it further for MI, go back to the original
idea of warning, only:

  https://sourceware.org/ml/gdb-patches/2010-08/msg00083.html

New test included.

gdb/ChangeLog:
2017-02-02  Pedro Alves  <palves@redhat.com>

	* cli/cli-logging.c (maybe_warn_already_logging): New factored out
	from ...
	(set_logging_overwrite): ... here.
	(logging_no_redirect_file): Delete.
	(set_logging_redirect): Don't handle redirection on the fly.
	Instead warn that "logging off" / "logging on" is necessary.
	(pop_output_files): Delete references to logging_no_redirect_file.
	(show_logging_command): Always speak in terms of what will happen
	once logging is reenabled.

gdb/testsuite/ChangeLog:
2017-02-02  Pedro Alves  <palves@redhat.com>

	* gdb.mi/mi-logging.exp: Add "redirect while already logging"
	tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Move "tee" building down to interpreter::set_logging_proc
@ 2017-02-02 22:23 sergiodj+buildbot
  2017-02-04  1:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-02 22:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 616268b639780e0819b51053c794037bcde3de16 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 616268b639780e0819b51053c794037bcde3de16

Move "tee" building down to interpreter::set_logging_proc

This patch gets rid of this hack in mi_set_logging:

      /* The tee created already is based on gdb_stdout, which for MI
	 is a console and so we end up in an infinite loop of console
	 writing to ui_file writing to console etc.  So discard the
	 existing tee (it hasn't been used yet, and MI won't ever use
	 it), and create one based on raw_stdout instead.  */

By pushing down responsibility for the tee creation to the
interpreter.  I.e., pushing the CLI bits out of handle_redirections
down to the CLI interpreter's set_logging_proc method.

This fixes a few leaks that I spotted, and then confirmed with
"valgrind --leak-check=full":

[...]
  ==21429== 56 (32 direct, 24 indirect) bytes in 1 blocks are definitely lost in loss record 30,243 of 34,980
  ==21429==    at 0x4C29216: operator new(unsigned long) (vg_replace_malloc.c:334)
  ==21429==    by 0x62D9A9: mi_set_logging(interp*, int, ui_file*, ui_file*) (mi-interp.c:1395)
  ==21429==    by 0x810B8A: current_interp_set_logging(int, ui_file*, ui_file*) (interps.c:360)
  ==21429==    by 0x61C537: handle_redirections(int) (cli-logging.c:162)
  ==21429==    by 0x61C6EC: set_logging_on(char*, int) (cli-logging.c:190)
  ==21429==    by 0x6163BE: do_cfunc(cmd_list_element*, char*, int) (cli-decode.c:105)
  ==21429==    by 0x6193C1: cmd_func(cmd_list_element*, char*, int) (cli-decode.c:1913)
  ==21429==    by 0x8DB790: execute_command(char*, int) (top.c:674)
  ==21429==    by 0x632AE6: mi_execute_cli_command(char const*, int, char const*) (mi-main.c:2343)
  ==21429==    by 0x6329BA: mi_cmd_execute(mi_parse*) (mi-main.c:2306)
  ==21429==    by 0x631E19: captured_mi_execute_command(ui_out*, mi_parse*) (mi-main.c:1998)
  ==21429==    by 0x632389: mi_execute_command(char const*, int) (mi-main.c:2163)
  ==21429==
[...]
  ==26635== 24 bytes in 1 blocks are definitely lost in loss record 20,740 of 34,995
  ==26635==    at 0x4C29216: operator new(unsigned long) (vg_replace_malloc.c:334)
  ==26635==    by 0x61C355: handle_redirections(int) (cli-logging.c:131)
  ==26635==    by 0x61C6EC: set_logging_on(char*, int) (cli-logging.c:190)
  ==26635==    by 0x6163BE: do_cfunc(cmd_list_element*, char*, int) (cli-decode.c:105)
  ==26635==    by 0x6193C1: cmd_func(cmd_list_element*, char*, int) (cli-decode.c:1913)
  ==26635==    by 0x8DB7BC: execute_command(char*, int) (top.c:674)
  ==26635==    by 0x7B9132: command_handler(char*) (event-top.c:590)
  ==26635==    by 0x7B94F7: command_line_handler(char*) (event-top.c:780)
  ==26635==    by 0x7B8ABB: gdb_rl_callback_handler(char*) (event-top.c:213)
  ==26635==    by 0x933CE9: rl_callback_read_char (callback.c:220)
  ==26635==    by 0x7B89ED: gdb_rl_callback_read_char_wrapper_noexcept() (event-top.c:175)
  ==26635==    by 0x7B8A49: gdb_rl_callback_read_char_wrapper(void*) (event-top.c:192)

One is fixed by transfering ownership of the log file to the tee.  In
pseudo-patch, since the code was moved at the same time:

 -     out = new tee_file (curr_output, false, logfile.get (), false);
 +     out = new tee_file (curr_output, false, logfile.get (), true);

The other is this bit in mi_set_logging:

    else
      {
 +      delete mi->raw_stdout;

I tried to split the leak fixes to a smaller preparatory patch, but
that was difficult exactly because of the tee hack in
handle_redirections -> mi_set_logging.

gdb/ChangeLog:
2017-02-02  Pedro Alves  <palves@redhat.com>

	* cli/cli-interp.c (struct saved_output_files, saved_output):
	Moved from cli/cli-logging.c.
	(cli_set_logging): New function.
	(cli_interp_procs): Install cli_set_logging.
	* cli/cli-interp.h (make_logging_output, cli_set_logging):
	Declare.
	* cli/cli-logging.c (struct saved_output_files, saved_output):
	Moved to cli/cli-interp.c.
	(pop_output_files): Don't save outputs here.
	(make_logging_output): New function.
	(handle_redirections): Don't build tee nor save previous outputs
	here.
	* interps.c (current_interp_set_logging): Change prototype.
	Assume there's always a set_logging_proc method installed.
	* interps.h (interp_set_logging_ftype): Change prototype.
	(current_interp_set_logging): Change prototype and adjust comment.
	* mi/mi-interp.c (mi_set_logging): Change protototype.  Adjust to
	use make_logging_output.
	* tui/tui-interp.c (tui_interp_procs): Install cli_set_logging.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] BFD: Wrap overlong error handler call line in `elf_gc_sweep'
@ 2017-02-02 23:22 sergiodj+buildbot
  2017-02-04  5:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-02 23:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f56d4fd28b887cc709524b1993c9da4c64b0696 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 8f56d4fd28b887cc709524b1993c9da4c64b0696

BFD: Wrap overlong error handler call line in `elf_gc_sweep'

	bfd/
	* elflink.c (elf_gc_sweep): Wrap overlong line.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Fix assertion in `mips_elf_sort_hash_table'
@ 2017-02-02 23:37 sergiodj+buildbot
  2017-02-04  9:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-02 23:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17a80fa80adbe79df39ba1fc70e611dff92df197 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 17a80fa80adbe79df39ba1fc70e611dff92df197

MIPS/BFD: Fix assertion in `mips_elf_sort_hash_table'

Move the assertion on non-NULL `htab' in `mips_elf_sort_hash_table' to
the beginning, before the pointer is dereferenced (`mips_elf_hash_table
(info)' and `elf_hash_table (info)' both point to the same memory
location, differently typed).

	bfd/
	* elfxx-mips.c (mips_elf_sort_hash_table): Move assertion on
	non-NULL `htab' to the beginning.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Respect the ELF gABI dynamic symbol table sort requirement
@ 2017-02-03  0:13 sergiodj+buildbot
  2017-02-04 21:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-03  0:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e17b0c351f0b22fb42edf34e5a6e486d72e9ee05 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: e17b0c351f0b22fb42edf34e5a6e486d72e9ee05

MIPS/BFD: Respect the ELF gABI dynamic symbol table sort requirement

Ensure all local symbols precede external symbols in the dynamic symbol
table.

No local symbols are expected to make it to the dynamic symbol table
except for section symbols already taken care of, so this is really a
safeguard only against a potential BFD bug otherwise not so harmful,
which may become a grave one due to a symbol table sorting requirement
violation (see PR ld/20828 for an example).  This means however that no
test suite coverage is possible for this change as code introduced here
is not normally expected to trigger.

Logically split then the part of the dynamic symbol table which is not
global offset table mapped, into a local area at the beginning and an
external area following.  By the time `mips_elf_sort_hash_table' is
called we have the number of local dynamic symbol table entries (section
and non-section) already counted in `local_dynsymcount', so use it to
offset the external area from the beginning.

	bfd/
	* elfxx-mips.c (mips_elf_hash_sort_data): Add
	`max_local_dynindx'.
	(mips_elf_sort_hash_table): Handle it.
	(mips_elf_sort_hash_table_f) <GGA_NONE>: For forced local
	symbols bump up `max_local_dynindx' rather than
	`max_non_got_dynindx'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix "maintenance selftest" printing stray instructions
@ 2017-02-03  0:38 sergiodj+buildbot
  2017-02-05  5:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-03  0:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b1ace6bdc2063f3dcf46172db98bb3474b6e1121 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b1ace6bdc2063f3dcf46172db98bb3474b6e1121

Fix "maintenance selftest" printing stray instructions

The "maintenance selftest" command is printing odd bits of stray
instructions like:

~~~
brkwarning: A handler for the OS ABI "GNU/Linux" is not built into this configuration
of GDB.  Attempting to continue with the default HS settings.


brkmov  r0, #0mov       r0, #0mov       r0, #0mov       r0, #0mov       r0, #0mov       r0, #0mov       r0, #0mov       r0, #0mov       r0, #0mov       r0, #0mov       r0, #0mov   r0, #0mov       r0, #0mov       r0, #0mov       r0, #0breakbreakbreakbreakbreakbreakbreakbreakbreakbreakbreakbreakbreakbreakbreakbreakbreakbreakbreakM3.L = 0xffff;/* ( -1) M3=0x0xffff(65535) */break 8break 8warning: A handler for the OS ABI "GNU/Linux" is not built into this configuration
of GDB.  Attempting to continue with the default cris:common_v10_v32 settings.
~~~

etc.  Those appear because here:

  class gdb_disassembler_test : public gdb_disassembler
  {
  public:

    const bool verbose = false;

    explicit gdb_disassembler_test (struct gdbarch *gdbarch,
				    const gdb_byte *insn,
				    size_t len)
      : gdb_disassembler (gdbarch,
			  (verbose ? gdb_stdout : &null_stream),
			  gdb_disassembler_test::read_memory),


specifically in this line:

			  (verbose ? gdb_stdout : &null_stream),

"verbose" has not been initialized yet, because the order of
initialization is base classes first, then members.  I.e. "verbose" is
only initialized after the base constructor is called.  Since the
gdb_disassembler_test object is created on the stack, "verbose" has
garbage at that point.  If the gargage is non-zero, then we end up
with the gdb_disassembler_test's stream incorrectly pointing to
gdb_stdout.

gdb/ChangeLog:
2017-02-02  Pedro Alves  <palves@redhat.com>

	* disasm-selftests.c (print_one_insn_test): Move the "verbose"
	field out of gdb_disassembler_test and make it static.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Streamline hash table references in `mips_elf_sort_hash_table'
@ 2017-02-03  1:31 sergiodj+buildbot
  2017-02-04 13:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-03  1:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f8c4b60ef3953a2373992e468106ae833049fff ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 0f8c4b60ef3953a2373992e468106ae833049fff

MIPS/BFD: Streamline hash table references in `mips_elf_sort_hash_table'

Make all hash table references throughout `mips_elf_sort_hash_table' use
`htab', simplifying code and improving readability.

	bfd/
	* elfxx-mips.c (mips_elf_sort_hash_table): Use `htab' throughout
	to access the hash table.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix compile time warning messages when compiling binutils with gcc 7.0.1.
@ 2017-02-03  9:19 sergiodj+buildbot
  2017-02-05 22:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-03  9:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b7e3d2fb7036ce6f9d74e32dc052518f5cd45b6 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 1b7e3d2fb7036ce6f9d74e32dc052518f5cd45b6

Fix compile time warning messages when compiling binutils with gcc 7.0.1.

	PR 21096
bfd	* coffcode.h (coff_write_object_contents): Enlarge size of
	s_name_buf in order to avoid compile time warning about possible
	integer truncation.
	* elf32-nds32.c (nds32_elf_ex9_import_table): Mask off lower
	32-bits of insn value before printing into buffer.

opcodes	* aarch64-opc.c (print_register_list): Ensure that the register
	list index will fir into the tb buffer.
	(print_register_offset_address): Likewise.
	* tic6x-dis.c (print_insn_tic6x): Increase size of func_unit_buf.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [BZ 21005] Add support for Intel 64 rdrand and rdseed record/replay
@ 2017-02-06  9:31 sergiodj+buildbot
  2017-02-06 22:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-06  9:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20b477a75c00de06a92b9577fd74416699d2c37f ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 20b477a75c00de06a92b9577fd74416699d2c37f

[BZ 21005] Add support for Intel 64 rdrand and rdseed record/replay

This patch addresses BZ 21005, which is gdb failing to recognize an rdrand
instruction.

It enables support for both rdrand and rdseed and handles extended register
addressing (R8~R15) for 16-bit, 32-bit and 64-bit.

gdb/ChangeLog
2017-02-06  Luis Machado  <lgustavo@codesourcery.com>

	* NEWS: Mention support for record/replay of Intel 64 rdrand and
	rdseed instructions.
	i386-tdep.c (i386_process_record): Handle Intel 64 rdrand and rseed.

gdb/testsuite/ChangeLog:
2017-02-06  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.reverse/insn-reverse.c: Include insn-reverse-x86.c.
	* gdb.reverse/insn-reverse-x86.c: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ARC] Provide an interface to decode ARC instructions.
@ 2017-02-06 10:53 sergiodj+buildbot
  2017-02-07  3:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-06 10:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ec7c1ae19e9e1bf2edad5125941a2fd5fdfde0b ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 6ec7c1ae19e9e1bf2edad5125941a2fd5fdfde0b

[ARC] Provide an interface to decode ARC instructions.

gas/
2017-02-06  Claudiu Zissulescu  <claziss@synopsys.com>

	* config/tc-arc.c (parse_opcode_flags): Ignore implicit flags.

include/
2017-02-06  Claudiu Zissulescu  <claziss@synopsys.com>
	    Anton Kolesov  <anton.kolesov@synopsys.com>

	* opcode/arc.h (insn_class_t): Add ENTER, LEAVE, POP, PUSH, BBIT0,
	BBIT1, BI, BIH, BRCC, EI, JLI, and SUB instruction classes.
	(flag_class_t): Add F_CLASS_WB, F_CLASS_ZZ, and F_CLASS_IMPLICIT
	flag classes.

opcode/
2017-02-06  Claudiu Zissulescu  <claziss@synopsys.com>
	    Anton Kolesov  <anton.kolesov@synopsys.com>

	* arc-dis.c (arc_disassemble_info): New structure.
	(init_arc_disasm_info): New function.
	(find_format_from_table): Ignore implicit flags.
	(find_format): Update dissassembler private data.
	(print_flags): Likewise.
	(print_insn_arc): Likewise.
	(arc_opcode_to_insn_type): Consider the new added instruction
	classes.
	(arcAnalyzeInstr): Remove.
	(arc_insn_decode): New function.
	* arc-dis.h (arc_ldst_writeback_mode): New enum.
	(arc_ldst_data_size): Likewise.
	(arc_condition_code): Likewise.
	(arc_operand_kind): Likewise.
	(arc_insn_kind): New struct.
	(arc_instruction): Likewise.
	(arc_insn_decode): Declare function.
	(ARC_Debugger_OperandType): Deleted.
	(Flow): Likewise.
	(NullifyMode): Likewise.
	(allOperandsSize): Likewise.
	(arcDisState): Likewise.
	(arcAnalyzeInstr): Likewise.
	* arc-dis.c (arc_opcode_to_insn_type): Handle newly introduced
	insn_class_t enums.
	* arc-opc.c (F_SIZED): New define.
	(C_CC_EQ, C_CC_GE, C_CC_GT, C_CC_HI, C_CC_HS): Likewise.
	(C_CC_LE, C_CC_LO, C_CC_LS, C_CC_LT, C_CC_NE): Likewise.
	(C_CC_NE, C_AA_AB, C_AA_AW, C_ZZ_D, C_ZZ_H, C_ZZ_B): Likewise.
	(arc_flag_classes): Add F_CLASS_COND/F_CLASS_IMPLICIT flags.
	* opcodes/arc-tbl.h: Update instructions to include new
	F_CLASS_IMPLICIT flags.
	(bbit0, lp): Change class.
	(bbit1, bi, bih, br*, ei_s, jli_s): Likewsie


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] bfd: Fix objdump --dynamic-reloc for SPARC 64-bit to show symbol names.
@ 2017-02-07 14:25 sergiodj+buildbot
  2017-02-07 15:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-07 14:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d044c0c78c11968b4fe3c5c019523e3177b1710 ***

Author: Sheldon Lobo <sheldon.lobo@oracle.com>
Branch: master
Commit: 3d044c0c78c11968b4fe3c5c019523e3177b1710

bfd: Fix objdump --dynamic-reloc for SPARC 64-bit to show symbol names.

Fixes ld/testsuite/ld-elf/shared.exp "Build libpr16496b.so".

The root cause is in bfd/elf64-sparc.c, elf64_sparc_slurp_one_reloc_table(),
bfd_get_symcount() was used for dynamic mode as well. The fix is to use
bfd_get_dynamic_symcount().

This has been tested with sparc64-linux-gnu, and it does not introduce any
regressions.

bfd/ChangeLog:

2017-02-06  Sheldon Lobo  <sheldon.lobo@oracle.com>

	Fix sparc64 dynamic relocation processing to use the dynamic
        symbol count.
	* elf64-sparc.c (elf64_sparc_slurp_one_reloc_table): Use 'dynamic'
	to determine if bfd_get_symcount() or bfd_get_dynamic_symcount()
	should be used.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: fix ARI warning in sparc-tdep.c
@ 2017-02-07 21:40 sergiodj+buildbot
  2017-02-07 23:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-07 21:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1291063deab60b735429411b29eea9d7fd68d50e ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 1291063deab60b735429411b29eea9d7fd68d50e

gdb: fix ARI warning in sparc-tdep.c

gdb/ChangeLog:

2017-02-07  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* sparc-tdep.c (sparc32_gdbarch_init): Do not place a + operator
	at the end of the line.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Command names: make them case sensitive
@ 2017-02-08 18:32 sergiodj+buildbot
  2017-02-08 20:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-08 18:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d7b173c29900879c9a5958dd6029fd36666e57c ***

Author: Jerome Guitton <guitton@adacore.com>
Branch: master
Commit: 3d7b173c29900879c9a5958dd6029fd36666e57c

Command names: make them case sensitive

Case-insensitive search for command names is an obscure undocumented
feature, which seems to be unused, is not tested and not quite
consistent. Remove it.

gdb/ChangeLog:

	* cli-decode.c (lookup_cmd_1, lookup_cmd_composition):
	Remove case-insensitive search.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Eliminate interp::quiet_p
@ 2017-02-08 20:52 sergiodj+buildbot
  2017-02-09  4:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-08 20:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a474bd8eeea16b2b6aa7089dedb142d86c22a4d7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a474bd8eeea16b2b6aa7089dedb142d86c22a4d7

Eliminate interp::quiet_p

This commit removes interp::quiet_p / interp_quiet_p /
interp_set_quiet, because AFAICS, it doesn't really do anything.

interp_quiet is only ever checked inside interp_set nowadays:

  if (!first_time && !interp_quiet_p (interp))
    {
      xsnprintf (buffer, sizeof (buffer),
		 "Switching to interpreter \"%.24s\".\n", interp->name);
      current_uiout->text (buffer);
    }

I did a bit of archaelogy, and found that back in 4a8f6654 (2003), it
was also called in another place, to decide whether to print the CLI
prompt.

AFAICS, that condition is always false today, making that if/then
block always dead code.  If we remove that code, then there are no
interp_quiet_p uses left in the tree, so we can remove it all.

There are two paths that lead to interp_set calls:

#1 - When installing the top level interpreter.  In this case,
FIRST_TIME is true.

#2 - In interpreter_exec_cmd.  In this case, the interpreter is always
set quiet before interp_set is called.

Grepping a gdb.log of an x86_64 GNU/Linux run for "Switching to
interpreter" (before this patch) doesn't find any hits.

I suspect the intention of this message was to support something like
a "set interpreter ..." command that would change the interpreter
permanently.  But there's no such command.

Tested on x86_64 Fedora 23.

gdb/ChangeLog:
2017-02-08  Pedro Alves  <palves@redhat.com>

	* interps.c (interp::interp): Remove reference to quiet_p.
	(interp_set): Make static.  Remove dead "Switching to" output
	code.
	(interp_quiet_p, interp_set_quiet): Delete.
	(interpreter_exec_cmd): Don't set the interpreter quiet.
	* interps.h (interp_quiet_p): Make static.
	(class interp) <quiet_p>: Remove field


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix NULL pointer dereference
@ 2017-02-09 15:56 sergiodj+buildbot
  2017-02-09 17:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-09 15:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff6fa24786eb2c03c1af95e2559fa3fd0b2f3893 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: ff6fa24786eb2c03c1af95e2559fa3fd0b2f3893

Fix NULL pointer dereference

This commit fixes a segmentation fault on tab completion when
certain debuginfo is installed:

  https://bugzilla.redhat.com/show_bug.cgi?id=1398387

gdb/ChangeLog:

	* symtab.c (add_symtab_completions): Prevent NULL pointer
	dereference.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] POWER9 add scv/rfscv instruction support
@ 2017-02-10  8:52 sergiodj+buildbot
  2017-02-10 10:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-10  8:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dce75bf9848c88583377c608e9734a2f8616d12b ***

Author: Nicholas Piggin <npiggin@gmail.com>
Branch: master
Commit: dce75bf9848c88583377c608e9734a2f8616d12b

POWER9 add scv/rfscv instruction support

opcodes/
	* ppc-opc.c (powerpc_opcodes) <scv, rfscv>: New mnemonics.

gas/
	* testsuite/gas/ppc/power9.d <scv, rfscv>: New tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb/MAINTAINERS: Update my e-mail address
@ 2017-02-10 18:09 sergiodj+buildbot
  2017-02-10 23:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-10 18:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f67f945cf2f6361d4c4997c487b174e396d23cd9 ***

Author: Martin Galvan <martingalvan@sourceware.org>
Branch: master
Commit: f67f945cf2f6361d4c4997c487b174e396d23cd9

gdb/MAINTAINERS: Update my e-mail address

gdb/ChangeLog:

2017-02-10  Martin Galvan  <martingalvan@sourceware.org>

        * MAINTAINERS (Write After Approval): Update my e-mail address.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove some ui_out-related cleanups from Python
@ 2017-02-10 20:08 sergiodj+buildbot
  2017-02-11  4:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-10 20:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d4b0bb186e204f77ed70bc719d16c6ca302094fd ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: d4b0bb186e204f77ed70bc719d16c6ca302094fd

Remove some ui_out-related cleanups from Python

This patch introduces a bit of infrastructure -- namely, a minimal
std::optional analogue called gdb::optional, and an RAII template
class that works like make_cleanup_ui_out_tuple_begin_end or
make_cleanup_ui_out_list_begin_end -- and then uses these in the
Python code.  This removes a number of cleanups and generally
simplifies this code.

std::optional is only available in C++17.  Normally I would have had
this code check __cplusplus, but my gcc apparently isn't new enough to
find <optional>, even with -std=c++1z; so, because I could not test
it, the patch does not do this.

gdb/ChangeLog
2017-02-10  Tom Tromey  <tom@tromey.com>

	* ui-out.h (ui_out_emit_type): New class.
	(ui_out_emit_tuple, ui_out_emit_list): New typedefs.
	* python/py-framefilter.c (py_print_single_arg): Use gdb::optional
	and ui_out_emit_tuple.
	(enumerate_locals): Likewise.
	(py_mi_print_variables, py_print_locals, py_print_args): Use
	ui_out_emit_list.
	(py_print_frame): Use gdb::optional, ui_out_emit_tuple,
	ui_out_emit_list.
	* common/gdb_optional.h: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove unnecessary local variables
@ 2017-02-11  0:55 sergiodj+buildbot
  2017-02-12  0:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-11  0:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d8365c48f797c7b947623eed8b1285d98323b68 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 2d8365c48f797c7b947623eed8b1285d98323b68

Remove unnecessary local variables

I found an unused local variables in a couple of places in the Python
code; this removes them.

gdb/ChangeLog
2017-02-10  Tom Tromey  <tom@tromey.com>

	* python/py-value.c (valpy_richcompare_throw): Remove unnecessary
	"cleanup" local.
	* python/py-type.c (typy_legacy_template_argument): Remove
	unnecessary "cleanup" local.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove unused variable in rust-lang.c
@ 2017-02-11  5:11 sergiodj+buildbot
  2017-02-12  9:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-11  5:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b145e37a29cd96e567293dc69c0fd4f8af243b9 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 0b145e37a29cd96e567293dc69c0fd4f8af243b9

Remove unused variable in rust-lang.c

I found another unused "cleanup" local variable, this time in
rust-lang.c.  This patch removes it.  Committing as obvious.

gdb/ChangeLog
2017-02-10  Tom Tromey  <tom@tromey.com>

	* rust-lang.c (rust_get_disr_info): Remove unused variable.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Improve load command's help text
@ 2017-02-13 15:27 sergiodj+buildbot
  2017-02-13 23:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-13 15:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5cf30ebf64d3c6da961094c615a94d2f1682a478 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 5cf30ebf64d3c6da961094c615a94d2f1682a478

Improve load command's help text

This fairly obvious patch adds usage text to the load command's help text.

Originally it did not have usage and mentioned things like FILE and OFFSET
without explaining how those should be passed in the command.

gdb/ChangeLog:

2017-02-13  Luis Machado  <lgustavo@codesourcery.com>

	* symfile (_initialize_symfile): Add usage text to the load command's
	help text.

gdb/doc/ChangeLog:

2017-02-13  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.texinfo (Target Commands): Document the optional offset
	argument for the load command.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] btrace: Count gaps as one instruction explicitly.
@ 2017-02-14 10:42 sergiodj+buildbot
  2017-02-14 15:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-14 10:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 69090ceead6fa841669eea0c81b3e8e9695def5f ***

Author: Tim Wiederhake <tim.wiederhake@intel.com>
Branch: master
Commit: 69090ceead6fa841669eea0c81b3e8e9695def5f

btrace: Count gaps as one instruction explicitly.

This gives all instructions, including gaps, a unique number.  Add a function
to retrieve the error code if a btrace instruction iterator points to an
invalid instruction.

Signed-off-by: Tim Wiederhake <tim.wiederhake@intel.com>

gdb/ChangeLog:

	* btrace.c (ftrace_call_num_insn, btrace_insn_get_error): New function.
	(ftrace_new_function, btrace_insn_number, btrace_insn_cmp,
	btrace_find_insn_by_number): Remove special case for gaps.
	* btrace.h (btrace_insn_get_error): New export.
	(btrace_insn_number, btrace_find_insn_by_number): Adjust comment.
	* record-btrace.c (btrace_insn_history): Print number for gaps.
	(record_btrace_info, record_btrace_goto): Handle gaps.

Change-Id: I8eb0e48a95f4278522fea74ea13526bfe6898ecc


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] python: Implement btrace Python bindings for record history.
@ 2017-02-14 17:02 sergiodj+buildbot
  2017-02-15 18:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-14 17:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 75c0bdf484b7a949a53b04edd95edca5f4662184 ***

Author: Tim Wiederhake <tim.wiederhake@intel.com>
Branch: master
Commit: 75c0bdf484b7a949a53b04edd95edca5f4662184

python: Implement btrace Python bindings for record history.

This patch implements the gdb.Record Python object methods and fields for
record target btrace.  Also, implement a stub for record target full.

Signed-off-by: Tim Wiederhake <tim.wiederhake@intel.com>

gdb/ChangeLog:

	* Makefile.in (SUBDIR_PYTHON_OBS): Add py-record-btrace.o,
	py-record-full.o.
	(SUBDIR_PYTHON_SRCS): Add py-record-btrace.c, py-record-full.c.
	* python/py-record-btrace.c, python/py-record-btrace.h,
	python/py-record-full.c, python/py-record-full.h: New file.
	* python/py-record.c: Add include for py-record-btrace.h and
	py-record-full.h.
	(recpy_method, recpy_format, recpy_goto, recpy_replay_position,
	recpy_instruction_history, recpy_function_call_history, recpy_begin,
	recpy_end): Use functions from py-record-btrace.c and py-record-full.c.
	* python/python-internal.h (PyInt_FromSsize_t, PyInt_AsSsize_t):
	New definition.
	(gdbpy_initialize_btrace): New export.
	* python/python.c (_initialize_python): Add gdbpy_initialize_btrace.

Change-Id: I8bd893672ffc7e619cc1386767897249e125973a


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Update ppc64_elf_gc_mark_dynamic_ref
@ 2017-02-14 19:24 sergiodj+buildbot
  2017-02-16  6:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-14 19:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e278ae05839ccffa234e0bfb4286b9f9a9dfbd28 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: e278ae05839ccffa234e0bfb4286b9f9a9dfbd28

Update ppc64_elf_gc_mark_dynamic_ref

	* elf64-ppc.c (ppc64_elf_gc_mark_dynamic_ref): Support
	--gc-keep-exported, and test versioned field of sym rather than
	looking for @ in name.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix illegal upper case gdb cmd in chained-calls.exp
@ 2017-02-15 12:11 sergiodj+buildbot
  2017-02-17 17:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-15 12:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b58a8c0c83d58c8f4be67dc1d7a1d9a5e1edba82 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: b58a8c0c83d58c8f4be67dc1d7a1d9a5e1edba82

Fix illegal upper case gdb cmd in chained-calls.exp

3d7b173c29900879c9a5958dd6029fd36666e57c made upper case commands now
illegal. However gdb.cp/chained-calls.exp still contains one test using
P to print an expression. This patch fixes the testcase to use p
instead.

2017-02-13  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	gdb/
	* gdb.cp/chained-calls.exp: Use p instead of P.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [AArch64] Add SVE system registers
@ 2017-02-15 17:26 sergiodj+buildbot
  2017-02-18  2:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-15 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 773fb663445646ebe45298e255d263f9520b2e2e ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 773fb663445646ebe45298e255d263f9520b2e2e

[AArch64] Add SVE system registers

This patch adds the SVE-specific system registers.

opcodes/
	* aarch64-opc.c (aarch64_sys_regs): Add SVE registers.
	(aarch64_sys_reg_supported_p): Handle them.

gas/
	* testsuite/gas/aarch64/sve-sysreg.s,
	testsuite/gas/aarch64/sve-sysreg.d,
	testsuite/gas/aarch64/sve-sysreg-invalid.d,
	testsuite/gas/aarch64/sve-sysreg-invalid.l: New tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] i386: Allow "lea foo@GOT, %reg" in PIC
@ 2017-02-15 21:34 sergiodj+buildbot
  2017-02-18 13:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-15 21:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a5684011edabf5804abb9e11253a9747587b284 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 2a5684011edabf5804abb9e11253a9747587b284

i386: Allow "lea foo@GOT, %reg" in PIC

"lea foo@GOT, %reg" is OK in PIC since it only loads the GOT offset
into register, which can be used later with a GOT base register to
get the value in the GOT entry.

bfd/

	PR ld/21168
	* elf32-i386.c (elf_i386_relocate_section): Allow
	"lea foo@GOT, %reg" in PIC.

ld/

	PR ld/21168
	* testsuite/ld-i386/i386.exp: Run pr21168.
	* testsuite/ld-i386/pr21168a.c: New file.
	* testsuite/ld-i386/pr21168b.S: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for Intel PKRU register to GDB and GDBserver.
@ 2017-02-17 11:43 sergiodj+buildbot
  2017-02-21  0:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-17 11:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51547df62c155231530ca502c485659f3d2b66cb ***

Author: Michael Sturm <michael.sturm@intel.com>
Branch: master
Commit: 51547df62c155231530ca502c485659f3d2b66cb

Add support for Intel PKRU register to GDB and GDBserver.

This patch adds support for the registers added by the
Memory Protection Keys for Userspace (PKU aka PKEYs) feature.
Native and remote debugging are covered by this patch.

The XSAVE area is extended with a new state containing
the 32-bit wide PKRU register. The new register is added to
amd64-avx-mpx_avx512-* tdesc, thus it is renamed accordingly. Also,
respective xstate mask X86_XSTATE_AVX_MPX_AVX512_MASK is renamed to
X86_XSTATE_AVX_MPX_AVX512_PKU_MASK to reflect the new feature set
it supports.

For more information, please refer to the
Intel(R) 64 and IA-32 Architectures Software Developer's
Manual - Septemper 2015
http://www.intel.com/content/dam/www/public/us/en/documents/
manuals/64-ia-32-architectures-software-developer-manual-325462.pdf

gdb/Changelog:
2015-12-08  Michael Sturm  <michael.sturm@intel.com>

     * NEWS: Mention addition of PKU feature.
     * amd64-linux-nat.c (amd64_linux_gregset32_reg_offset): Add PKRU register.
     * amd64-linux-tdep.c (features/i386/amd64-avx-mpx-avx512-linux.c): Rename
       to...
     (features/i386/amd64-avx-mpx-avx512-pku-linux.c): ...this.
     (amd64_linux_gregset_reg_offset): Add PKRU register.
     (amd64_linux_core_read_description): Rename
     X86_XSTATE_AVX_MPX_AVX512_MASK,
     rename tdesc_amd64_avx_mpx_avx512_pku_linux.
     (_initialize_amd64_linux_tdep): Rename
     initialize_tdesc_amd64_avx_mpx_avx512_linux.
     * amd64-linux-tdep.h (AMD64_LINUX_ORIG_RAX_REGNUM): Adjust regnum
     calculation.
     (tdesc_amd64_avx_mpx_avx512_linux): Rename to...
     (tdesc_amd64_avx_mpx_avx512_pku_linux): ...this.
     * amd64-tdep.c (features/i386/amd64-avx-mpx-avx512-pku.c): Rename to...
     (features/i386/amd64-avx-mpx-avx512-pku.c): ...this.
     (amd64_pkeys_names): New register name for raw register PKRU.
     (amd64_init_abi): Add code to initialize PKRU tdep variables if feature
     is present.
     (amd64_target_description): Rename X86_XSTATE_AVX_MPX_AVX512_MASK,
     rename tdesc_amd64_avx_mpx_avx512.
     (_initialize_amd64_tdep): Rename initialize_tdesc_amd64_avx_mpx_avx512.
     * amd64-tdep.h (enum amd64_regnum): Add PKRU register.
     (AMD64_NUM_REGS): Adjust regnum calculation.
     * i386-linux.nat.c (GETXSTATEREGS_SUPPLIES): Extend range of
     registers supplied via XSTATE by PKRU register.
     * common/x86-xstate.h (X86_XSTATE_PKRU): New macro.
     (X86_XSTATE_AVX_MPX_AVX512_MASK): Add PKRU and renamed mask.
     (X86_XSTATE_ALL_MASK): Rename X86_XSTATE_AVX_MPX_AVX512_MASK.
     (X86_XSTATE_PKRU_SIZE): New macro.
     (X86_XSTATE_MAX_SIZE): Adjust size.
     (HAS_PKRU(XCR0)): New macro.
     (X86_XSTATE_SIZE): Add checkfor PKRU.
     * features/Makefile (WHICH): Rename i386/i386-avx-mpx-avx512,
     i386/i386-avx-mpx-avx512-linux, i386/amd64-avx-mpx-avx512,
     i386/amd64-avx-mpx-avx512-linux.
     (i386/i386-avx-mpx-avx512-expedite): Rename expedite.
     (i386/i386-avx-mpx-avx512-linux-expedite): Likewise.
     (i386/amd64-avx-mpx-avx512-expedite): Likewise.
     (i386/amd64-avx-mpx-avx512-linux-expedite): Likewise.
     (XMLTOC): Rename i386/amd64-avx-mpx-avx512-linux.xml,
     i386/amd64-avx-mpx-avx512.xml, i386/i386-avx-mpx-avx512-linux.xml,
     i386/i386-avx-mpx-avx512.xml.
     ((outdir)/i386/i386-avx-mpx-avx512.dat): Rename rule, add
     i386/32bit-pkeys.xml.
     ((outdir)/i386/i386-avx-mpx-avx512-pku-linux.dat): Likewise.
     ((outdir)/i386/amd64-avx-mpx-avx512.dat): Rename rule, add
     i386/64bit-pkeys.xml.
     ((outdir)/i386/amd64-avx-mpx-avx512-linux.dat): Likewise.
     * features/i386/32bit-pkeys.xml: New file.
     * features/i386/64bit-pkeys.xml: Likewise.
     * features/i386/amd64-avx-mpx-avx512-linux-pku.c: Regenerate from
     renamed XML file.
     * features/i386/amd64-avx-mpx-avx512-linux.xml: Rename to
     amd64-avx-mpx-avx512-pku-linux.xml, add 64bit-pkeys.xml
     * features/i386/amd64-avx-mpx-avx512.c: Regenerate from
     renamed XML file.
     * features/i386/amd64-avx-mpx-avx512.xml: Rename to
     amd64-avx-mpx-avx512-pku.xml, add 64bit-pkeys.xml.
     * features/i386/i386-avx-mpx-avx512-linux.c: Regenerate from
     renamed XML file.
     * features/i386/i386-avx-mpx-avx512-linux.xml: Rename to
     i386-avx-mpx-avx512-pku-linux.xml, add 32bit-pkeys.xml.
     * features/i386/i386-avx-mpx-avx512.c: Regenerate from
     renamed XML file.
     * features/i386/i386-avx-mpx-avx512.xml: Rename to
     i386-avx-mpx-avx512-pku.xml, add 32bit-pkeys.xml.
     * i386-linux-nat.c (GETXSTATEREGS_SUPPLIES): Change to use
     I386_PKEYS_NUM_REGS.
     * i386-linux-tdep.c (features/i386/i386-avx-mpx-avx512-linux.c): Rename
     include.
     (i386_linux_gregset_reg_offset): Add PKRU register.
     (i386_linux_core_read_description): Rename xstate mask and returned
     tdesc for X86_XSTATE_AVX_MPX_AVX512_PKU_MASK.
     (_initialize_i386_linux_tdep): Rename
     initialize_tdesc_i386_avx_mpx_avx512_linux.
     * i386-linux-tdep.h (I386_LINUX_ORIG_EAX_REGNUM): Adjuste regnum
     calculation.
     (tdesc_i386_avx_mpx_avx512_linux): Rename prototype.
     (/* Format of XSAVE...): Add pkru register.
     * i386-tdep.c (i386-avx-mpx-avx512.c): Rename include.
     (i386_pkeys_names): New register name for raw register PKRU.
     (i386_pkru_regnum_p): Add function to look up register number of
     PKRU raw register.
     (i386_register_reggroup_p): Add code to exclude PKRU from general
     register group.
     (i386_validate_tdesc_p): Add code to handle PKRU feature, add PKRU
     registers if feature is present in xcr0.
     (i386_gdbarch_init): Adjust number of registers in architecture. Add code
     to initialize PKRU feature variables in tdep structure.
     (i386_target_description): Rename xstate mask and returned
     tdesc for X86_XSTATE_AVX_MPX_AVX512_PKU_MASK.
     (_initialize_i386_tdep): Rename initialize_tdesc_i386_avx_mpx_avx512.
     * i386-tdep.h (struct gdbarch_tdep): Add feature variables to tdep
     structure.
     (enum i386_regnum): Add PKRU register.
     (I386_PKEYS_NUM_REGS): New define for number of registers in PKRU feature.
     (i386_pkru_regnum_p): New prototype.
     * i387-tdep.c (xsave_pkeys_offset): New table for PKRU offsets in
     XSAVE buffer.
     (XSAVE_PKEYS_ADDR): New macro.
     (i387_supply_xsave): Add code to handle PKRU register.
     (i387_collect_xsave): Likewise.
     * i387-tdep.h (I387_NUM_PKEYS_REGS): New define for number of registers
     in PKRU feature.
     (I387_PKRU_REGNUM): New macro.
     (I387_PKEYSEND_REGNUM): Likewise.
     * regformats/i386/amd64_avx_mpx_avx512_pku_linux.dat: Regenerate from
     renamed XML file.
     * regformats/i386/amd64_avx_mpx_avx512_pku.dat: Likewise.
     * regformats/i386/i386/amd64-avx-mpx-avx512-pku.dat: Likewise.
     * regformats/i386/i386_avx_mpx_avx512_pku_linux.dat: Likewise.

testsuite/Changelog:
2016-04-18  Michael Sturm  <michael.sturm@intel.com>

     * gdb.arch/i386-pkru.c: New file.
     * gdb.arch/i386-pkru.exp: Likewise.

gdbserver/Changelog:
2016-04-18  Michael Sturm  <michael.sturm@intel.com>

     * Makefile.in (clean): Rename i386-avx-mpx-avx512.c,
     i386-avx-mpx-avx512-linux.c, amd64-avx-mpx-avx512.c,
     amd64-avx-mpx-avx512-linux.c.
     (i386-avx-mpx-avx512-linux-ipa.o:): Rename rule and source file.
     (amd64-avx-mpx-avx512-linux-ipa.o:): Likewise.
     (i386-avx-mpx-avx512.c :): Rename rule, source files and dat files.
     (i386-avx-mpx-avx512-linux.c :): Likewise.
     (amd64-avx-mpx-avx512.c :): Likewise.
     (amd64-avx-mpx-avx512-linux.c :): Likewise.
     * configure.srv (srv_i386_regobj): Rename i386-avx-mpx-avx512.o.
     (srv_i386_linux_regobj): Rename i386-avx-mpx-avx512-linux.o.
     (srv_amd64_regobj): Rename amd64-avx-mpx-avx512.o.
     (srv_amd64_linux_regobj): Rename amd64-avx-mpx-avx512-linux.o.
     (ipa_i386_linux_regobj): Rename i386-avx-mpx-avx512-linux-ipa.o.
     (ipa_amd64_linux_regobj): Rename amd64-avx-mpx-avx512-pku-linux-ipa.o.
     (srv_i386_32bit_xmlfiles): Add 32bit-pkeys.xml.
     (srv_i386_64bit_xmlfiles): Add 64bit-pkeys.xml.
     (srv_i386_xmlfiles): Rename i386/i386-avx-mpx-avx512.xml.
     (srv_amd64_xmlfiles): Rename i386/amd64-avx-mpx-avx512.xml.
     (srv_i386_linux_xmlfiles): Rename i386/i386-avx-mpx-avx512-linux.xml.
     (srv_amd64_linux_xmlfiles): Rename di386/amd64-avx-mpx-avx512-linux.xml.
     * i387-fp.c (num_pkeys_registers): New variable.
     (struct i387_xsave): Add space for pkru values.
     (i387_cache_to_fsave): Add code to handle PKRU register.
     (i387_xsave_to_cache): Likewise.
     * linux-amd64-ipa.c (get_ipa_tdesc): Rename
     tdesc_amd64_avx_mpx_avx512_linux.
     (initialize_low_tracepoint): Rename
     init_registers_amd64_avx_mpx_avx512_linux.
     * linux-i386-ipa.c (get_ipa_desc): Rename
     tdesc_i386_avx_mpx_avx512_linux.
     (initialize_low_tracepoint): Rename
     init_registers_i386_avx_mpx_avx512_linux.
     * linux-x86-low.c (x86_64_regmap[]): Add PKRU register.
     (x86_linux_read_description): Rename X86_XSTATE_AVX_MPX_AVX512_MASK,
     rename tdesc_amd64_avx_mpx_avx512_linux, rename
     tdesc_i386_avx_mpx_avx512_linux.
     (x86_get_ipa_tdesc_idx): Rename tdesc_amd64_avx_mpx_avx512_linux,
     rename tdesc_i386_avx_mpx_avx512_linux.
     (initialize_low_arch): Rename init_registers_amd64_avx_mpx_avx512_linux,
     rename init_registers_i386_avx_mpx_avx512_linux.
     * linux-x86-tdesc.h (init_registers_amd64_avx_mpx_avx512_linux): Renamed
     prototype.
     (tdesc_amd64_avx_mpx_avx512_linux): Likewise.
     (init_registers_i386_avx_mpx_avx512_linux): Likewise.
     (tdesc_i386_avx_mpx_avx512_linux): Likewise.

doc/Changelog:
2016-04-18  Michael Sturm  <michael.sturm@intel.com>

     * gdb.texinfo (i386 Features): Add description of PKRU register.

Change-Id: If75ce5aba7dfd33fdbe3d8b47f04ef3f550c52be
Signed-off-by: Michael Sturm <michael.sturm@intel.com>


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Code cleanup: Split dwarf2_ranges_read to a callback
@ 2017-02-20 20:58 sergiodj+buildbot
  2017-02-22  0:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-20 20:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f46c5a54825aabb3f30095c84ac30aff7400ac5 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 5f46c5a54825aabb3f30095c84ac30aff7400ac5

Code cleanup: Split dwarf2_ranges_read to a callback

DWARF-5 has .debug_rnglists which is somehow similar to .debug_ranges.

This patch converts dwarf2_ranges_read to dwarf2_ranges_process which can work
with both DWARF kinds of range lists through a callback.

It also simplifies dwarf2_record_block_ranges which can benefit from it.

gdb/ChangeLog
2017-02-20  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* dwarf2read.c (dwarf2_ranges_process): New function from
	dwarf2_ranges_read.
	(dwarf2_ranges_read, dwarf2_record_block_ranges): Use
	dwarf2_ranges_process.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase in gdb.arch/ppc64-atomic-inst.exp
@ 2017-02-21 14:17 sergiodj+buildbot
  2017-02-22 15:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-21 14:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a51d7ecf3ddd64e0aec68e3c30913faba680b2cb ***

Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Branch: master
Commit: a51d7ecf3ddd64e0aec68e3c30913faba680b2cb

Fix test names starting with uppercase in gdb.arch/ppc64-atomic-inst.exp

gdb/testsuite/
2017-02-21  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* gdb.arch/ppc64-atomic-inst.exp: Fix test names starting with
	uppercase.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [ppc64] Add POWER8/ISA 2.07 atomic sequences single-stepping support
@ 2017-02-21 15:39 sergiodj+buildbot
  2017-02-22 20:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-21 15:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2039d74e780db6659c87cd3c426d526615cfe703 ***

Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Branch: master
Commit: 2039d74e780db6659c87cd3c426d526615cfe703

[ppc64] Add POWER8/ISA 2.07 atomic sequences single-stepping support

gdb/
2017-02-21  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* rs6000-tdep.c (LOAD_AND_RESERVE_MASK): Rename from LWARX_MASK.
	(STORE_CONDITIONAL_MASK): Rename from STWCX_MASK.
	(LBARX_INSTRUCTION, LHARX_INSTRUCTION, LQARX_INSTRUCTION,
	STBCX_INSTRUCTION, STHCX_INSTRUCTION, STQCX_INSTRUCTION): New defines.
	(IS_LOAD_AND_RESERVE_INSN, IS_STORE_CONDITIONAL_INSN): New macros.
	(ppc_displaced_step_copy_insn): Use IS_LOAD_AND_RESERVE_INSN.
	(ppc_deal_with_atomic_sequence): Use IS_LOAD_AND_RESERVE_INSN and
	IS_STORE_CONDITIONAL_INSN.

gdb/testsuite/
2017-02-21  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* gdb.arch/ppc64-isa207-atomic-inst.exp: New testcase based on
	gdb.arch/ppc64-atomic-inst.exp.  Add tests for lbarx/stbcx, lharx/sthcx
	and lqarx/stqcx.
	* gdb.arch/ppc64-isa207-atomic-inst.S: New file.
	* gdb.arch/ppc64-isa207-atomic-inst.c: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PowerPC ld segfault on script discarding dynamic sections
@ 2017-02-21 23:12 sergiodj+buildbot
  2017-02-23  3:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-21 23:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6528b6eba85f044667876a2ad77d4612a9e5fc65 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 6528b6eba85f044667876a2ad77d4612a9e5fc65

PowerPC ld segfault on script discarding dynamic sections

bfd/
	* elf64-ppc.c (ppc64_elf_finish_dynamic_sections): Don't segfault
	on .got or .plt output section being discarded by script.
	* elf32-ppc.c (ppc_elf_finish_dynamic_sections): Likewise.  Move
	vxworks splt temp.
gold/
	* powerpc.cc (Target_powerpc::make_iplt_section): Check that
	output_section exists before attempting add_output_section_data.
	(Target_powerpc::make_brlt_section): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Align .gnu_debuglink sections on a 4-byte boundary.
@ 2017-02-22 17:45 sergiodj+buildbot
  2017-02-23 15:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-22 17:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 758d96d834ba725461abf4be36df9f13e0815054 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 758d96d834ba725461abf4be36df9f13e0815054

Align .gnu_debuglink sections on a 4-byte boundary.

	PR binutils/21193
	* opncls.c (bfd_create_gnu_debuglink_section): Give the newly
	created section 4-byte alignment.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: drop stray VEX opcode 82 references
@ 2017-02-23 10:18 sergiodj+buildbot
  2017-02-24  4:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-23 10:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53c4d625d70138fb5b75f0e2ebae8ff363ed3d46 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 53c4d625d70138fb5b75f0e2ebae8ff363ed3d46

x86: drop stray VEX opcode 82 references

No such ModR/M-less opcode has ever existed in public documentation
afaict, so I can't see why it had been added in the first place.
Furthermore opcode 77 is special only with implied prefix 0F.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix usage of inferior_ptid in two thread_alive implementations
@ 2017-02-23 15:54 sergiodj+buildbot
  2017-02-24 16:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-23 15:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8eaf53202ea60191162d5f1069cd08ebd9f38f6c ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8eaf53202ea60191162d5f1069cd08ebd9f38f6c

Fix usage of inferior_ptid in two thread_alive implementations

While inspecting some target code, I noticed that in these two
implementations of thread_alive, inferior_ptid is referenced directly
instead of using the ptid passed as parameters.  I guess that it is
wrong, although I can't really test it in both cases.

gdb/ChangeLog:

	* bsd-uthread.c (bsd_uthread_thread_alive): Use ptid instead of
	inferior_ptid.
	* go32-nat.c (go32_thread_alive): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] S/390: Add support for new cpu architecture - arch12.
@ 2017-02-23 20:15 sergiodj+buildbot
  2017-02-25  8:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-23 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64025b4ec97fe8e932c367c6cb719e5fcf2448e8 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 64025b4ec97fe8e932c367c6cb719e5fcf2448e8

S/390: Add support for new cpu architecture - arch12.

This adds support of new instructions to the S/390 specific parts.

The important feature of the new instruction set is the support of
single and extended precision floating point vector operations.

Note: arch12 is NOT the official name of the new CPU.  It just
continues the series of archXX options supported as alternate names.
The archXX terminology refers to the edition number of the Principle
of Operations manual.  The official CPU name will be added later while
keeping support of the arch12 for backwards compatibility.

No testsuite regressions.

Committed to mainline.

Bye,

-Andreas-

opcodes/ChangeLog:

2017-02-23  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-mkopc.c (main): Accept arch12 as cpu string and vx2 as
	facility.
	* s390-opc.c: Add new operand description macros, new instruction
	types, instruction masks, and new .insn instruction types.
	* s390-opc.txt: Add new arch12 instructions.

include/ChangeLog:

2017-02-23  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* opcode/s390.h (enum s390_opcode_cpu_val): New value
	S390_OPCODE_ARCH12.
	(S390_INSTR_FLAG_VX2): New macro definition.

gas/ChangeLog:

2017-02-23  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* config/tc-s390.c (s390_parse_cpu): New entry for arch12.
	* doc/as.texinfo: Document arch12 as cpu type.
	* doc/c-s390.texi: Likewise.
	* testsuite/gas/s390/s390.exp: Run arch12 specific tests.
	* testsuite/gas/s390/zarch-arch12.d: New test.
	* testsuite/gas/s390/zarch-arch12.s: New test.
	* testsuite/gas/s390/zarch-z13.d: Rename some mnemonics in the
	output patterns.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add new counter-enable CSRs
@ 2017-02-24 19:18 sergiodj+buildbot
  2017-02-26 12:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-24 19:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 742d14b39b384e822fd2218cf1803aef68a95d99 ***

Author: Andrew Waterman <andrew@sifive.com>
Branch: master
Commit: 742d14b39b384e822fd2218cf1803aef68a95d99

Add new counter-enable CSRs

include/ChangeLog:

2017-02-22  Andrew Waterman  <andrew@sifive.com>

       * opcode/riscv-opc.h (CSR_SCOUNTEREN): New define.
       (CSR_MCOUNTEREN): Likewise.
       (scounteren): Declare register.
       (mcounteren): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add missing smov support, and clean up existing umov support.
@ 2017-02-26  5:34 sergiodj+buildbot
  2017-02-27 16:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-26  5:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 152e1e1bc90030cec9ce8318ab982675b1e90a00 ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: 152e1e1bc90030cec9ce8318ab982675b1e90a00

Add missing smov support, and clean up existing umov support.

	sim/aarch64/
	* simulator.c (do_vec_SMOV_into_scalar): New.
	(do_vec_UMOV_into_scalar): Renamed from do_vec_MOV_into_scalar.
	Rewritten.
	(do_vec_UMOV): Merged into do_vec_UMOV_into_scalar and deleted.
	(do_vec_op1): Move do_vec_TRN call and do_vec_UZP call.  Add
	do_vec_SMOV_into_scalar call.  Delete do_vec_MOV_into_scalar and
	do_vec_UMOV calls.  Add do_vec_UMOV_into_scalar call.

	sim/testsuite/sim/aarch64/
	* sumov.s: New.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use range-based for loop in remote_add_target_side_condition
@ 2017-02-27 18:58 sergiodj+buildbot
  2017-02-28 21:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-27 18:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8362122330c97c8c4a15da4e7ba8aa29f0c11157 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8362122330c97c8c4a15da4e7ba8aa29f0c11157

Use range-based for loop in remote_add_target_side_condition

Using a range based for loop makes this code a bit more clean and
readable.

The comment above is clearly erroneous, so I've updated it.

gdb/ChangeLog:

	* remote.c (remote_add_target_side_condition): Use range-based
	for loop.  Update comment.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Also handle `jalr $0, $25' with R_MIPS_JALR
@ 2017-02-28  0:57 sergiodj+buildbot
  2017-03-01  5:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-28  0:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e39210161e7c547ab53afb86997303e24a42c0c ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 0e39210161e7c547ab53afb86997303e24a42c0c

MIPS/BFD: Also handle `jalr $0, $25' with R_MIPS_JALR

Interpret the `jalr $0, $25' instruction encoding with an R_MIPS_JALR
relocation attached as an alias to `jr $25' and convert the jump to an
equivalent branch where possible, consequently covering the MIPSr6
architecture for the purpose of this optimization too.

	bfd/
	* elfxx-mips.c (mips_elf_perform_relocation): Also handle the
	`jalr $0, $25' instruction encoding.

	gas/
	* testsuite/gas/mips/jalr4.s: Add `jalr $0, $25' instructions.
	* testsuite/gas/mips/jalr4.d: Adjust accordingly.  Remove MIPSr6
	encoding patterns.
	* testsuite/gas/mips/jalr4-n64.d: Likewise.
	* testsuite/gas/mips/mipsr6@jalr4.d: New test.
	* testsuite/gas/mips/mipsr6@jalr4-n32.d: New test.
	* testsuite/gas/mips/mipsr6@jalr4-n64.d: New test.

	ld/
	* testsuite/ld-mips-elf/jalr4.dd: Adjust for `jalr $0, $25'
	instructions.
	* testsuite/ld-mips-elf/jalr4-r6.dd: New test.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PowerPC addpcis fix
@ 2017-02-28  4:22 sergiodj+buildbot
  2017-03-01 13:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-28  4:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ba71655a425ac44721f97cc0ad7922ca15bce43 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 7ba71655a425ac44721f97cc0ad7922ca15bce43

PowerPC addpcis fix

This came up because I was looking at ld/tmpdir/addpcis.o and noticed
the odd addends on REL16DX_HA.  They ought to both be -4.  The error
crept in due REL16DX_HA howto being pc-relative (as indeed it should
be), and code at gas/write.c:1001 after this comment
	      /* Make it pc-relative.  If the back-end code has not
		 selected a pc-relative reloc, cancel the adjustment
		 we do later on all pc-relative relocs.  */
*not* cancelling the pc-relative adjustment.  So I've made a dummy
non-relative split reloc so that the generic code handles this, rather
than attempting to add hacks later in md_apply_fix which would not be
very robust.  Having the new internal reloc also makes it easy to
support

 addpcis rx,sym@ha

as an equivalent to

 addpcis rx,(sym-0f)@ha
0:

The patch also fixes overflow checking, which must test whether the
addi will overflow too since @l relocs don't have any overflow check.

Lastly, since I was poking at md_apply_fix, I arranged to have the
generic gas/write.c code emit errors for subtraction expressions where
we lack reloc support.

include/
	* elf/ppc64.h (R_PPC64_16DX_HA): New.  Expand fake reloc comment.
	* elf/ppc.h (R_PPC_16DX_HA): Likewise.
bfd/
	* reloc.c (BFD_RELOC_PPC_16DX_HA): New.
	* elf64-ppc.c (ppc64_elf_howto_raw <R_PPC64_16DX_HA>): New howto.
	(ppc64_elf_reloc_type_lookup): Translate new bfd reloc.
	(ppc64_elf_ha_reloc): Correct overflow test on REL16DX_HA.
	(ppc64_elf_relocate_section): Likewise.
	* elf32-ppc.c (ppc_elf_howto_raw <R_PPC_16DX_HA>): New howto.
	(ppc_elf_reloc_type_lookup): Translate new bfd reloc.
	(ppc_elf_check_relocs): Handle R_PPC_16DX_HA to pacify gcc.
	* libbfd.h: Regenerate.
	* bfd-in2.h: Regenerate.
gas/
	* config/tc-ppc.c (md_assemble): Use BFD_RELOC_PPC_16DX_HA for addpcis.
	(md_apply_fix): Remove fx_subsy check.  Move code converting to
	pcrel reloc earlier and handle BFD_RELOC_PPC_16DX_HA.  Remove code
	emiiting errors on seeing fx_pcrel set on unexpected relocs, as
	that is done now by the generic code via..
	* config/tc-ppc.h (TC_FORCE_RELOCATION_SUB_LOCAL): ..this. Define.
	(TC_VALIDATE_FIX_SUB): Define.
ld/
	* testsuite/ld-powerpc/addpcis.d: Define ext1 and ext2 at
	limits of addpcis range.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: fix handling of 64-bit operand size VPCMPESTR{I, M}
@ 2017-02-28 10:17 sergiodj+buildbot
  2017-03-01 22:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-02-28 10:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 15c7c1d8a535000e94ed36f4259d0ede32001408 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 15c7c1d8a535000e94ed36f4259d0ede32001408

x86: fix handling of 64-bit operand size VPCMPESTR{I,M}

Just like REX.W affects operand size of the implicit rAX/rDX inputs to
PCMPESTR{I,M}, VEX.W does for VPCMPESTR{I,M}. Allow Q or L suffixes on
the instructions.

Similarly the disassembler needs to be adjusted to no longer require
VEX.W to be zero for the instructions to be valid, and to emit proper
suffixes.

Note, however, that this doesn't address the problem of there being no
way to control (at least) {,E}VEX.W for 32- or 16-bit code. Nor does it
address the problem of the many WIG instructions not getting properly
disassembled when VEX.W=1.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PowerPC VLE typo fix
@ 2017-03-02  0:24 sergiodj+buildbot
  2017-03-02 17:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-02  0:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 673cff9b8b3105f74ce97c202a0727f9e83e56e6 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 673cff9b8b3105f74ce97c202a0727f9e83e56e6

PowerPC VLE typo fix

	* elf32-ppc.c (ppc_elf_vle_split16): Correct insn mask typo.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Align eh_frame FDEs according to their encoding
@ 2017-03-05  4:44 sergiodj+buildbot
  2017-03-05  6:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-05  4:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e0ce1c84d328bde4dca24b7cfc8b9c033ed271c ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 2e0ce1c84d328bde4dca24b7cfc8b9c033ed271c

Align eh_frame FDEs according to their encoding

bfd/
	* elf-bfd.h (struct eh_cie_fde): Add u.cie.per_encoding_aligned8.
	* elf-eh-frame.c (size_of_output_cie_fde): Don't align here.
	(next_cie_fde_offset): New function.
	(_bfd_elf_parse_eh_frame): Set u.cie.per_encoding_aligned8.
	(_bfd_elf_discard_section_eh_frame): Align zero terminator to
	four bytes.  Align CIEs to four or eight bytes depending on
	per_encoding_aligned8.  Align FDEs according to their encoding.
	Pad last FDE to output section alignment.
	(_bfd_elf_write_section_eh_frame): Adjust to suit.  Remove
	assertion.
	* elf64-ppc.c (glink_eh_frame_cie): Delete padding.
	(ppc64_elf_size_stubs): Pad glink eh_frame as per elf-eh-frame.c.
	(ppc64_elf_finish_dynamic_sections): Adjust to suit.
ld/
	* testsuite/ld-elf/eh3.d: Adjust for eh_frame alignment change.
	* testsuite/ld-elf/eh6.d: Likewise.
	* testsuite/ld-alpha/tlsbin.dd: Likewise.
	* testsuite/ld-alpha/tlsbin.td: Likewise.
	* testsuite/ld-alpha/tlsbinr.dd: Likewise.
	* testsuite/ld-alpha/tlspic.dd: Likewise.
	* testsuite/ld-alpha/tlspic.rd: Likewise.
	* testsuite/ld-alpha/tlspic.sd: Likewise.
	* testsuite/ld-alpha/tlspic.td: Likewise.
	* testsuite/ld-mips-elf/eh-frame1-n64.d: Likewise.
	* testsuite/ld-mips-elf/eh-frame2-n64.d: Likewise.
	* testsuite/ld-mips-elf/eh-frame3.d: Likewise.
	* testsuite/ld-x86-64/pr20830a.d: Likewise.
	* testsuite/ld-x86-64/pr21038a.d: Likewise.
	* testsuite/ld-x86-64/pr21038b.d: Likewise.
	* testsuite/ld-x86-64/pr21038c.d: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add describing intro comment to gdb.base/tui-layout.exp
@ 2017-03-07 14:45 sergiodj+buildbot
  2017-03-07 18:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-07 14:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f8c4e718c26a0181821398e09d96113c0ff49c15 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f8c4e718c26a0181821398e09d96113c0ff49c15

Add describing intro comment to gdb.base/tui-layout.exp

gdb/testsuite/ChangeLog:
2017-03-07  Pedro Alves  <palves@redhat.com>

	* gdb.base/tui-layout.exp: Add intro comment and fix typo.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Share gdb/environ.[ch] with gdbserver
@ 2017-03-07 21:08 sergiodj+buildbot
  2017-03-08 16:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-07 21:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1672e0d98d88d11b5c7d5793bd2cf29cbb56696f ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 1672e0d98d88d11b5c7d5793bd2cf29cbb56696f

Share gdb/environ.[ch] with gdbserver

We will need access to the environment functions when we share
fork_inferior between GDB and gdbserver, therefore we simply make the
API on gdb/environ.[ch] available on common/.  No extra adjustments
are needed to make it compile on gdbserver.

gdb/ChangeLog:
2017-03-07  Sergio Durigan Junior  <sergiodj@redhat.com>

	* Makefile.in (SFILES): Replace "environ.c" with
	"common/environ.c".
	(HFILES_NO_SRCDIR): Likewise, for "environ.h".
	* environ.c: Include "common-defs.h" instead of "defs.h.  Moved
	to...
	* common/environ.c: ... here.
	* environ.h: Moved to...
	* common/environ.h: ... here.

gdb/gdbserver/ChangeLog:
2017-03-07  Sergio Durigan Junior  <sergiodj@redhat.com>

	* Makefile.in (SFILES): Add "common/environ.c".
	(OBJS): Add "common/environ.h".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Move TUI testcases to new gdb/testsuite/gdb.tui/ directory
@ 2017-03-08  0:56 sergiodj+buildbot
  2017-03-08 19:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-08  0:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7cbbff33a502dcba0264a1935840345274b8aee2 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 7cbbff33a502dcba0264a1935840345274b8aee2

Move TUI testcases to new gdb/testsuite/gdb.tui/ directory

Let's start putting TUI tests in their own dir.

gdb/testsuite/
2017-03-08  Pedro Alves  <palves@redhat.com>

	* gdb.base/tui-disasm-long-lines.c,
	gdb.base/tui-disasm-long-lines.exp, gdb.base/tui-layout.c,
	gdb.base/tui-layout.exp: Move to ...
	* gdb.tui/: ... this new directory.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR tui/21216: TUI line breaks regression
@ 2017-03-08  2:52 sergiodj+buildbot
  2017-03-09  3:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-08  2:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9753a2f6d74dc92d2ad94993a5479ee0edbc6887 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 9753a2f6d74dc92d2ad94993a5479ee0edbc6887

Fix PR tui/21216: TUI line breaks regression

Commit d7e747318f4d04 ("Eliminate make_cleanup_ui_file_delete / make
ui_file a class hierarchy") regressed the TUI's command window.
Newlines miss doing a "carriage return", resulting in output like:

~~~~~~~~~~~~~~~~~~
(gdb) helpList of classes of commands:

                                      aliases -- Aliases of other commands
                                                                          breakpoints -- Making program stop at certain points
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Before the commit mentioned above, the default ui_file->to_write
implementation had a hack that would defer into the ui_file->to_fputs
method.  The TUI's ui_file did not implement the to_write method, so
all writes would end up going to the ncurses window via tui_file_fputs
-> tui_puts.

After the commit above, the hack is gone, but the TUI's ui_file still
does not implement the ui_file::write method.  Since tui_file inherits
from stdio_file, writing to a tui_file ends up doing fwrite on the
FILE stream the TUI is "associated" with, via stdio_file::write,
instead of writing to the ncurses window.

The fix is to have tui_file override the "write" method.

New test included.

gdb/ChangeLog:
2017-03-08  Pedro Alves  <palves@redhat.com>

	PR tui/21216
	* tui/tui-file.c (tui_file::write): New.
	* tui/tui-file.h (tui_file): Override "write".
	* tui/tui-io.c (do_tui_putc, update_start_line): New functions,
	factored out from ...
	(tui_puts): ... here.
	(tui_putc): Use them.
	(tui_write): New function.
	* tui/tui-io.h (tui_write): Declare.

gdb/testsuite/ChangeLog:
2017-03-08  Pedro Alves  <palves@redhat.com>

	PR tui/21216
	* gdb.tui/tui-nl-filtered-output.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] "gdb.arch/i386-pkru.exp: probe PKRU support" shouldn't FAIL if not supported
@ 2017-03-08 13:45 sergiodj+buildbot
  2017-03-09 15:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-08 13:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 25dcbff6ef0088e080d92b3cbc346ae0b5071d9d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 25dcbff6ef0088e080d92b3cbc346ae0b5071d9d

"gdb.arch/i386-pkru.exp: probe PKRU support" shouldn't FAIL if not supported

Currently I get:

 (gdb) print have_pkru()
 $1 = 0
 (gdb) FAIL: gdb.arch/i386-pkru.exp: probe PKRU support
 UNSUPPORTED: gdb.arch/i386-pkru.exp: processor does not support protection key feature.

Probing suceeded, so that should be a PASS -> UNSUPPORTED.

gdb/testsuite/ChangeLog:
2017-03-08  Pedro Alves  <palves@redhat.com>

	* gdb.arch/i386-pkru.exp (probe PKRU support): Handle detecting
	PKRU as not supported as a PASS.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add support for the new 'lnia' extended mnemonic.
@ 2017-03-08 20:33 sergiodj+buildbot
  2017-03-11 12:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-08 20:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1437d0631b209500db8371c425e896deb66ec9f9 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: 1437d0631b209500db8371c425e896deb66ec9f9

Add support for the new 'lnia' extended mnemonic.

opcodes/
	* ppc-opc.c (powerpc_opcodes) <lnia>: New extended mnemonic.

gas/
	* testsuite/gas/ppc/power9.d <lnia> New test.
	* testsuite/gas/ppc/power9.s: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Avoid unstable test message in gdb.base/step-over-exit.exp
@ 2017-03-08 22:52 sergiodj+buildbot
  2017-03-12  9:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-08 22:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1de05205afe1ecd1f1fa2befc6843d0dc70adefc ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1de05205afe1ecd1f1fa2befc6843d0dc70adefc

Avoid unstable test message in gdb.base/step-over-exit.exp

Currently diffing testrun results shows:

 -PASS: gdb.base/step-over-exit.exp: break *0x7ffff77e18c6 if main == 0
 +PASS: gdb.base/step-over-exit.exp: break *0x2aaaab0988c6 if main == 0

gdb/testsuite/ChangeLog:
2017-03-08  Pedro Alves  <palves@redhat.com>

	* gdb.base/step-over-exit.exp: Add explicit test message.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Update -maltivec and -mvsx options to only enable their oldest instructions.
@ 2017-03-09  3:06 sergiodj+buildbot
  2017-03-13  5:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-09  3:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b8b687e885287ed85dafffcebbb8d03d7ea2c38 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: 4b8b687e885287ed85dafffcebbb8d03d7ea2c38

Update -maltivec and -mvsx options to only enable their oldest instructions.

Currently, the -maltivec and -mvsx GAS options enable *all* of the altivec
and vsx instructions respecitively that have ever been added.  This is in
constract to GCC's -maltivec and -mvsx options, which only enable the oldest
(ie, first) set of altivec and vsx instructions.  This patch changes GAS to
mimic GCC's behaviour with respect to -maltivec and -mvsx and it solves a
problem with trying to assemble the lxvx instruction which is different
between POWER8 and POWER9.

opcodes/
	* ppc-dis.c (ppc_opts) <altivec>: Do not use PPC_OPCODE_ALTIVEC2;
	<vsx>: Do not use PPC_OPCODE_VSX3;

gas/
	* testsuite/gas/ppc/altivec2.d (as): Use the -mpower8 option.
	(objdump): Use the -Mpower8 option.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use CpuCET on rdsspq
@ 2017-03-09 16:05 sergiodj+buildbot
  2017-03-14  1:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-09 16:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1fe188b154a4e81372629316be3d3a7820efdac ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: c1fe188b154a4e81372629316be3d3a7820efdac

Use CpuCET on rdsspq

	* i386-opc.tbl: Use CpuCET on rdsspq.
	* i386-tbl.h: Regenerated.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix compile time warnings about using possibly uninitialised variables in rs6000-core.c.
@ 2017-03-09 16:53 sergiodj+buildbot
  2017-03-15 13:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-09 16:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f03265d9cda1f5f8df238efa9b7a20330e5711f1 ***

Author: Sam Thursfield <sam.thursfield@codethink.co.uk>
Branch: master
Commit: f03265d9cda1f5f8df238efa9b7a20330e5711f1

Fix compile time warnings about using possibly uninitialised variables in rs6000-core.c.

	* rs6000-core.c (CORE_NEW): Simplify macro when
	AIX_CORE_DUMPX_CORE and BFD64 are true to avoid compile warning.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Rename R_AARCH64_TLSDESC_LD64_LO12_NC to R_AARCH64_TLSDESC_LD64_LO12 and R_AARCH64_TLSDESC_ADD_LO12_NC to R_AARCH64_TLSDESC_ADD_LO12.
@ 2017-03-13 10:26 sergiodj+buildbot
  2017-03-24  8:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-13 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f955cccff399ccc4e16b8e90f140f2e9a785a07b ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: f955cccff399ccc4e16b8e90f140f2e9a785a07b

Rename R_AARCH64_TLSDESC_LD64_LO12_NC to R_AARCH64_TLSDESC_LD64_LO12 and R_AARCH64_TLSDESC_ADD_LO12_NC to R_AARCH64_TLSDESC_ADD_LO12.

	PR binutils/21202
include	* elf/aarch64.h (R_AARCH64_TLSDESC_LD64_LO12_NC): Rename to
	R_AARCH64_TLSDESC_LD64_LO12.
	(R_AARCH64_TLSDESC_ADD_LO12_NC): Rename to
	R_AARCH64_TLSDESC_ADD_LO12_NC.

bfd	* reloc.c (BFD_RELOC_AARCH64_TLSDESC_LD64_LO12_NC): Rename to
	BFD_RELOC_AARCH64_TLSDESC_LD64_LO12.
	(BFD_RELOC_AARCH64_TLSDESC_ADD_LO12_NC): Rename to
	BFD_RELOC_AARCH64_TLSDESC_ADD_LO12.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
	* elfnn-aarch64.c (IS_AARCH64_TLS_RELAX_RELOC): Update reloc
	names.
	(IS_AARCH64_TLSDESC_RELOC): Likewise.
	(elfNN_aarch64_howto_table): Likewise.
	(aarch64_tls_transition_without_check): Likewise.
	(aarch64_reloc_got_type): Likewise.
	(elfNN_aarch64_final_link_relocate): Likewise.
	(elfNN_aarch64_tls_relax): Likewise.
	(elfNN_aarch64_relocate_section): Likewise.
	(elfNN_aarch64_gc_sweep_hook): Likewise.
	(elfNN_aarch64_check_relocs): Likewise.
	* elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
	(_bfd_aarch64_elf_resolve_relocation): Likewise.

gas	* config/tc-aarch64.c (reloc_table): Rename
	BFD_RELOC_AARCH64_TLSDESC_LD64_LO12_NC to
	BFD_RELOC_AARCH64_TLSDESC_LD64_LO12.  Rname
	BFD_RELOC_AARCH64_TLSDESC_ADD_LO12_NC to
	BFD_RELOC_AARCH64_TLSDESC_ADD_LO12.
	(md_apply_fix): Likewise.
	(aarch64_force_relocation): Likewise.
	* testsuite/gas/aarch64/tls.d: Update regexp.

ld	* testsuite/ld-aarch64/ifunc-5r-local.d: Update regexp.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbserver: Use pattern rule for objects from common/
@ 2017-03-22  1:38 sergiodj+buildbot
  2017-03-31  6:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22  1:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6bda016bec556855c6d4e191f360f921faa40ded ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 6bda016bec556855c6d4e191f360f921faa40ded

gdbserver: Use pattern rule for objects from common/

gdb/gdbserver/ChangeLog:

	* Makefile.in (%.o: ../common/%.c): New rule.
	(signals.o: ../common/signals.c): Remove.
	(print-utils.o: ../common/print-utils.c): Remove.
	(rsp-low.o: ../common/rsp-low.c): Remove.
	(common-utils.o: ../common/common-utils.c): Remove.
	(posix-strerror.o: ../common/posix-strerror.c): Remove.
	(mingw-strerror.o: ../common/mingw-strerror.c): Remove.
	(vec.o: ../common/vec.c): Remove.
	(gdb_vecs.o: ../common/gdb_vecs.c): Remove.
	(xml-utils.o: ../common/xml-utils.c): Remove.
	(ptid.o: ../common/ptid.c): Remove.
	(buffer.o: ../common/buffer.c): Remove.
	(format.o: ../common/format.c): Remove.
	(filestuff.o: ../common/filestuff.c): Remove.
	(agent.o: ../common/agent.c): Remove.
	(errors.o: ../common/errors.c): Remove.
	(environ.o: ../common/environ.c): Remove.
	(common-debug.o: ../common/common-debug.c): Remove.
	(cleanups.o: ../common/cleanups.c): Remove.
	(common-exceptions.o: ../common/common-exceptions.c): Remove.
	(fileio.o: ../common/fileio.c): Remove.
	(common-regcache.o: ../common/common-regcache.c): Remove.
	(signals-state-save-restore.o: ../common/signals-state-save-restore.c): Remove.
	(new-op.o: ../common/new-op.c): Remove.
	(btrace-common.o: ../common/btrace-common.c): Remove.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Introduce regcache_get_ptid
@ 2017-03-22  2:06 sergiodj+buildbot
  2017-04-05 11:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22  2:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ddaaf0fb8605fced72e84410fc7ac834e529eb53 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: ddaaf0fb8605fced72e84410fc7ac834e529eb53

Introduce regcache_get_ptid

This patch introduces the regcache_get_ptid function, which can be used
to retrieve the ptid a regcache is connected to.  It is used in
subsequent patches.

gdb/ChangeLog:

	* regcache.h (regcache_get_ptid): New function.
	* regcache.c (regcache_get_ptid): New function.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] amd64-linux-nat: Use ptid from regcache instead of inferior_ptid
@ 2017-03-22  2:36 sergiodj+buildbot
  2017-04-07  4:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22  2:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6a06fbb7b73fe55d6b9057f8154652e1ae8f883c ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 6a06fbb7b73fe55d6b9057f8154652e1ae8f883c

amd64-linux-nat: Use ptid from regcache instead of inferior_ptid

gdb/ChangeLog:

	* amd64-linux-nat.c (amd64_linux_fetch_inferior_registers,
	amd64_linux_fetch_inferior_registers): Use regcache->ptid
	instead of inferior_ptid.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] aix-thread: Use ptid from regcache instead of inferior_ptid
@ 2017-03-22  3:39 sergiodj+buildbot
  2017-04-08 22:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22  3:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edb5fb00a6865884f99be01a9e97f44243a9deb9 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: edb5fb00a6865884f99be01a9e97f44243a9deb9

aix-thread: Use ptid from regcache instead of inferior_ptid

gdb/ChangeLog:

	* aix-thread.c (aix_thread_fetch_registers,
	aix_thread_store_registers): Use regcache->ptid instead of
	inferior_ptid.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix expect for gdb.cp/m-static.exp
@ 2017-03-22  7:47 sergiodj+buildbot
  2017-04-18  9:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22  7:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec3b243d4308ee56c9e3c62470b10ed2a822eb51 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: ec3b243d4308ee56c9e3c62470b10ed2a822eb51

Fix expect for gdb.cp/m-static.exp

The expectation in gdb.cp/m-static.exp for the ptype of
single_constructor is to get in the result of destructor with the
following prototype: ~single_constructor(int).

Yet, m-static.cc declares the destructor as ~single_constructor(). This
commit fixes the expectation.

2017-03-16  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	gdb/testsuite/
	* gdb.cp/m-static.exp: Fix expectation for prototype of
	test5.single_constructor and single_constructor::single_constructor.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] E6500 spr mnemonics
@ 2017-03-22 12:43 sergiodj+buildbot
  2017-04-28  6:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22 12:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b94dd2de12dd0389615700b13b63260e162ccf0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 4b94dd2de12dd0389615700b13b63260e162ccf0

E6500 spr mnemonics

	PR 21248
	* ppc-opc.c (powerpc_opcodes): Enable mfivor32, mfivor33,
	mtivor32, and mtivor33 for e6500.  Move mfibatl and mfibatu after
	those spr mnemonics they alias.  Similarly for mtibatl, mtibatu.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix PR gdb/19637: bound_registers.py: Add support for Python 3
@ 2017-03-22 13:04 sergiodj+buildbot
  2017-04-29 15:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22 13:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7503099f3e29739d34cb1224d54fba96404e6e61 ***

Author: Jonah Graham <jonah@kichwacoders.com>
Branch: master
Commit: 7503099f3e29739d34cb1224d54fba96404e6e61

Fix PR gdb/19637: bound_registers.py: Add support for Python 3

Fix this the same way gdb/python/lib/gdb/printing.py handles it.

gdb/Changelog:
2017-03-17  Jonah Graham  <jonah@kichwacoders.com>

	PR gdb/19637
	* python/lib/gdb/printer/bound_registers.py: Add support for
	Python 3.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] hppa-obsd-nat: Use ptid from regcache instead of inferior_ptid
@ 2017-03-22 17:59 sergiodj+buildbot
  2017-05-06 20:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22 17:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bbe1eef1e585e19d5493882e55f2b7902df9827a ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: bbe1eef1e585e19d5493882e55f2b7902df9827a

hppa-obsd-nat: Use ptid from regcache instead of inferior_ptid

gdb/ChangeLog:

	* hppa-obsd-nat.c (hppaobsd_fetch_registers,
	hppaobsd_store_registers): Use ptid from regcache.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] i386-gnu-nat: Use ptid from regcache instead of inferior_ptid
@ 2017-03-22 19:22 sergiodj+buildbot
  2017-05-09 10:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22 19:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9cb6cdcfa12368f2f639f8cd06d18b94bd98a39 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: d9cb6cdcfa12368f2f639f8cd06d18b94bd98a39

i386-gnu-nat: Use ptid from regcache instead of inferior_ptid

gdb/ChangeLog:

	* i386-gnu-nat.c (gnu_fetch_registers, gnu_store_registers): Use
	ptid from regcache.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add DW_OP_GNU_variable_value
@ 2017-03-22 20:08 sergiodj+buildbot
  2017-04-15 19:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22 20:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c98763221af696a9e0c6686da7d65881bfd6bdd0 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: c98763221af696a9e0c6686da7d65881bfd6bdd0

Add DW_OP_GNU_variable_value

Sync GCC dwarf.def change

2017-03-14  Jakub Jelinek  <jakub@redhat.com>

	PR debug/77589
	* dwarf2.def (DW_OP_GNU_variable_value): New opcode.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add ability to return rvalue reference values from value_ref
@ 2017-03-22 23:28 sergiodj+buildbot
  2017-05-18  6:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-22 23:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a65cfae5f8b268158c23a862e7a996d15bbcef0e ***

Author: Artemiy Volkov <artemiyv@acm.org>
Branch: master
Commit: a65cfae5f8b268158c23a862e7a996d15bbcef0e

Add ability to return rvalue reference values from value_ref

Parameterize value_ref() by the kind of reference type the value of which
is requested. Change all callers to use the new API.

gdb/ChangeLog

	PR gdb/14441
	* ada-lang.c (ada_evaluate_subexp): Adhere to the new
	value_ref() interface.
	* c-valprint.c (c_value_print): Likewise.
	* infcall.c (value_arg_coerce): Likewise.
	* python/py-value.c (valpy_reference_value): Likewise.
	* valops.c (value_cast, value_reinterpret_cast)
	(value_dynamic_cast, typecmp): Likewise.
	(value_ref): Parameterize by kind of return value reference type.
	* value.h (value_ref): Add new parameter "refcode".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Support DW_TAG_rvalue_reference type
@ 2017-03-23  0:29 sergiodj+buildbot
  2017-05-21 22:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-23  0:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4297a3f0029974c62628d69b6f3f9ef25f01ea7d ***

Author: Artemiy Volkov <artemiyv@acm.org>
Branch: master
Commit: 4297a3f0029974c62628d69b6f3f9ef25f01ea7d

Support DW_TAG_rvalue_reference type

Make gdb DWARF reader understand the DW_TAG_rvalue_reference type tag. Handling
of this tag is done in the existing read_tag_reference_type() function, to
which we add a new parameter representing the kind of reference type
(lvalue vs rvalue).

gdb/ChangeLog

	PR gdb/14441
	* dwarf2read.c (process_die, read_type_die_1): Handle the
	DW_TAG_rvalue_reference_type DIE.
	(read_tag_reference_type): Add new parameter "refcode".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add rvalue references to overloading resolution
@ 2017-03-23  1:42 sergiodj+buildbot
  2017-05-24 17:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-23  1:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 15c0a2a9305648095f5586a02b5a5017e1643e99 ***

Author: Artemiy Volkov <artemiyv@acm.org>
Branch: master
Commit: 15c0a2a9305648095f5586a02b5a5017e1643e99

Add rvalue references to overloading resolution

This patch introduces changes to rank_one_type() dealing with ranking an rvalue
reference type when selecting a best viable function from a set of candidate
functions. The 4 new added rules for rvalue references are:

1) An rvalue argument cannot be bound to a non-const lvalue reference parameter
and an lvalue argument cannot be bound to an rvalue reference parameter.
[C++11 13.3.3.1.4p3]

2) If a conversion to one type of reference is an identity conversion, and a
conversion to the second type of reference is a non-identity conversion, choose
the first type. [C++11 13.3.3.2p3]

3) An rvalue should be first tried to bind to an rvalue reference, and then to
an lvalue reference. [C++11 13.3.3.2p3]

4) An lvalue reference to a function gets higher priority than an rvalue
reference to a function. [C++11 13.3.3.2p3]

This patch is not exactly correct.  See c++/15372 for tracking overload
resolution bugs.

gdb/ChangeLog

	PR gdb/14441
	* gdbtypes.c (rank_one_type): Implement overloading
	resolution rules regarding rvalue references.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove AARCH64_RECORD_FAILURE
@ 2017-03-23 15:04 sergiodj+buildbot
  2017-06-07 15:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-23 15:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0eef9404b0fcfc8b0fbe7511d094a419ac631e9 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: a0eef9404b0fcfc8b0fbe7511d094a419ac631e9

Remove AARCH64_RECORD_FAILURE

It is not used at all.

gdb:

2017-03-23  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c: Remove AARCH64_RECORD_FAILURE.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove MAX_REGISTER_SIZE from sol-thread.c
@ 2017-03-23 16:19 sergiodj+buildbot
  2017-06-10 11:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-23 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 077ae656a69fcf144f68848a3f6f2cb559b62987 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 077ae656a69fcf144f68848a3f6f2cb559b62987

Remove MAX_REGISTER_SIZE from sol-thread.c

gdb/
	* sol-thread.c (sol_thread_store_registers): Remove regcache calls.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Change {lookup,make}_reference_type API
@ 2017-03-24  7:12 sergiodj+buildbot
  2017-05-17  9:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-24  7:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b22433085e4cfee83f5c52f3baa8fb9bc67f8dd ***

Author: Artemiy Volkov <artemiyv@acm.org>
Branch: master
Commit: 3b22433085e4cfee83f5c52f3baa8fb9bc67f8dd

Change {lookup,make}_reference_type API

Parameterize lookup_reference_type() and make_reference_type() by the kind of
reference type we want to look up. Create two wrapper functions
lookup_{lvalue,rvalue}_reference_type() for lookup_reference_type() to simplify
the API. Change all callers to use the new API.

gdb/Changelog

	PR gdb/14441
	* dwarf2read.c (read_tag_reference_type): Use
	lookup_lvalue_reference_type() instead of lookup_reference_type().
	* eval.c (evaluate_subexp_standard): Likewise.
	* f-exp.y: Likewise.
	* gdbtypes.c (make_reference_type, lookup_reference_type):
	Generalize with rvalue reference types.
	(lookup_lvalue_reference_type, lookup_rvalue_reference_type): New
	convenience wrappers for lookup_reference_type().
	* gdbtypes.h (make_reference_type, lookup_reference_type): Add a
	reference kind parameter.
	(lookup_lvalue_reference_type, lookup_rvalue_reference_type): Add
	wrappers for lookup_reference_type().
	* guile/scm-type.c (gdbscm_type_reference): Use
	lookup_lvalue_reference_type() instead of lookup_reference_type().
	* guile/scm-value.c (gdbscm_value_dynamic_type): Likewise.
	* parse.c (follow_types): Likewise.
	* python/py-type.c (typy_reference, typy_lookup_type): Likewise.
	* python/py-value.c (valpy_get_dynamic_type, valpy_getitem):
	Likewise.
	* python/py-xmethods.c (gdbpy_get_xmethod_result_type)
	(gdbpy_invoke_xmethod): Likewise.
	* stabsread.c: Provide extra argument to make_reference_type()
	call.
	* valops.c (value_ref, value_rtti_indirect_type): Use
	lookup_lvalue_reference_type() instead of lookup_reference_type().


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Avoid segfault on invalid directory table
@ 2017-03-24 15:38 sergiodj+buildbot
  2017-06-12  6:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-24 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 568c1b9f503649d19ed1d17e6970f212e6b6317d ***

Author: Pdraig Brady <pbrady@fb.com>
Branch: master
Commit: 568c1b9f503649d19ed1d17e6970f212e6b6317d

Avoid segfault on invalid directory table

gdb was segfaulting during backtrace on a binary here, where
fe->dir_index parsed from the DWARF info was seen to access beyond the
provided include_dirs array.

This commit bounds the access to entries actually written to the
array, and was verified to output the backtrace correctly.

gdb/ChangeLog:

	* dwarf2read.c (setup_type_unit_groups): Ensure dir_index doesn't
	reference beyond the 'lh->include_dirs' array before accessing to
	it.
	(psymtab_include_file_name): Likewise.
	(dwarf_decode_lines_1): Likewise.
	(dwarf_decode_lines): Likewise.
	(file_file_name): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add rvalue reference tests and docs
@ 2017-03-24 16:24 sergiodj+buildbot
  2017-05-25 13:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-24 16:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0f55cc689a57deb342b988b8f0ecb908f0a76e1 ***

Author: Artemiy Volkov <artemiyv@acm.org>
Branch: master
Commit: c0f55cc689a57deb342b988b8f0ecb908f0a76e1

Add rvalue reference tests and docs

This patch adds tests for the initial rvalue reference support patchset.  All
of the new tests are practically mirrored regular references tests and, except
for the demangler ones, are introduced in new files, which are set to be
compiled with -std=gnu++11.  Tested are printing of rvalue reference types and
values, rvalue reference parameters in function overloading, demangling of
function names containing rvalue reference parameters, casts to rvalue
reference types, application of the sizeof operator to rvalue reference types
and values, and support for rvalue references within the gdb python module.

gdb/ChnageLog

	PR gdb/14441
	* NEWS: Mention support for rvalue references in GDB and python.
	* doc/gdb.texinfo (C Plus Plus Expressions): Mention that GDB
	supports both lvalue and rvalue references.

gdb/testsuite/ChangeLog

	PR gdb/14441
	* gdb.cp/demangle.exp: Add rvalue reference tests.
	* gdb.cp/rvalue-ref-casts.cc: New file.
	* gdb.cp/rvalue-ref-casts.exp: New file.
	* gdb.cp/rvalue-ref-overload.cc: New file.
	* gdb.cp/rvalue-ref-overload.exp: New file.
	* gdb.cp/rvalue-ref-params.cc: New file.
	* gdb.cp/rvalue-ref-params.exp: New file.
	* gdb.cp/rvalue-ref-sizeof.cc: New file.
	* gdb.cp/rvalue-ref-sizeof.exp: New file.
	* gdb.cp/rvalue-ref-types.cc: New file.
	* gdb.cp/rvalue-ref-types.exp: New file.
	* gdb.python/py-rvalue-ref-value-cc.cc: New file.
	* gdb.python/py-rvalue-ref-value-cc.exp: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc/nps400: Add cp16/cp32 instructions to opcodes library
@ 2017-03-24 21:27 sergiodj+buildbot
  2017-05-29 22:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-24 21:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 645d3342ba2b920722991255513030bb903b794e ***

Author: Rinat Zelig <rinat@mellanox.com>
Branch: master
Commit: 645d3342ba2b920722991255513030bb903b794e

arc/nps400: Add cp16/cp32 instructions to opcodes library

Instructions for loading or storing 16/32B data from one address type to
another.

gas/ChangeLog

	* testsuite/gas/arc/nps400-11.s: New file.
	* testsuite/gas/arc/nps400-11.d: New file.

include/ChangeLog

	* opcode/arc.h (insn_class_t): Add DMA class.

opcodes/ChangeLog

	* arc-nps400-tbl.h: Add cp32/cp16 instructions format.
	* arc-opc.c: Add F_NPS_NA, NPS_DMA_IMM_ENTRY, NPS_DMA_IMM_OFFSET.
	(insert_nps_imm_offset): New function.
	(extract_nps_imm_offset): New function.
	(insert_nps_imm_entry): New function.
	(extract_nps_imm_entry): New function.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove some unnecessary inferior_ptid setting/restoring when fetching/storing registers
@ 2017-03-25 10:49 sergiodj+buildbot
  2017-06-11  8:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-25 10:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e00d44febb8093d8dc0e6842b975afb194c4fd1 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 3e00d44febb8093d8dc0e6842b975afb194c4fd1

Remove some unnecessary inferior_ptid setting/restoring when fetching/storing registers

Now that the to_fetch_registers, to_store_registers and
to_prepare_to_store target methods don't rely on the value of
inferior_ptid anymore, we can remove a bunch of now unnecessary setting
and restoring of inferior_ptid.

The asserts added recently in target_fetch_registers and
target_store_registers, which validate that inferior_ptid matches the
regcache's ptid, must go away.  It's the whole point of this effort, to
not require inferior_ptid to have a particular value when calling these
functions.

One thing that I noticed is how sol-thread.c's ps_lgetregs and friends
use the current value of inferior_ptid instead of what's passed as
argument (ph->ptid), unlike proc-service.c's versions of the same
functions.  Is it expected?  I left it like this in the current patch,
but unless there's a good reason for it to be that way, I guess we
should make it use the parameter.

gdb/ChangeLog:

	* fbsd-tdep.c (fbsd_corefile_thread): Don't set/restore
	inferior_ptid.
	* proc-service.c (ps_lgetregs, ps_lsetregs, ps_lgetfpregs,
	ps_lsetfpregs): Likewise.
	* regcache.c (regcache_raw_update, regcache_raw_write): Likewise.
	* sol-thread.c (ps_lgetregs, ps_lsetregs, ps_lgetfpregs,
	ps_lsetfpregs): Likewise.
	* target.c (target_fetch_registers, target_store_registers):
	Remove asserts.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add minimal support for WebAssembly backend to the BFD library.
@ 2017-03-27 11:49 sergiodj+buildbot
  2017-06-16  1:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-27 11:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8fb740dd3032543b833b141011aa2005c035d024 ***

Author: Pip Cet <pipcet@gmail.com>
Branch: master
Commit: 8fb740dd3032543b833b141011aa2005c035d024

Add minimal support for WebAssembly backend to the BFD library.

include * elf/wasm32.h: New file to support wasm32 architecture.

bfd * cpu-wasm32.c: New file to support wasm32 architecture.
    * elf32-wasm32.c: New file to support wasm32 architecture.
    * Makefile.am: Add wasm32 architecture.
    * archures.c: Likewise.
    * config.bfd: Likewise.
    * configure.ac: Likewise.
    * targets.c: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR21303, objdump doesn't show e200z4 insns
@ 2017-03-27 11:50 sergiodj+buildbot
  2017-06-17 18:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-27 11:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b7539374617a94c2d646f49e1bbfc954b11891d ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 9b7539374617a94c2d646f49e1bbfc954b11891d

PR21303, objdump doesn't show e200z4 insns

	PR 21303
opcodes/
	* ppc-dis.c (struct ppc_mopt): Comment.
	(ppc_opts <e200z4>): Move PPC_OPCODE_VLE from .sticky to .cpu.
gas/
	* testsuite/gas/ppc/pr21303.d,
	* testsuite/gas/ppc/pr21303.s: New test
	* testsuite/gas/ppc/ppc.exp: Run it.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb/cp-name-parser.y: Eliminate make_empty, use cplus_demangle_fill_component
@ 2017-03-27 15:29 sergiodj+buildbot
  2017-06-21 21:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-27 15:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a7e80b9e21eb907ac5c90de7452588c059db0cec ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a7e80b9e21eb907ac5c90de7452588c059db0cec

gdb/cp-name-parser.y: Eliminate make_empty, use cplus_demangle_fill_component

The demangler exports the cplus_demangle_fill_component function that
clients should use to initialize demangle_component components that
use the "s_binary" union member.  cp-name-parser.y uses it in some
places, via the fill_comp wrapper, but not all.  Several places
instead use a GDB-specific "make_empty" function.  Because this
function does not call any of the demangler "fill" functions, we had
to patch it recently to clear the allocated demangle_component's
"d_printing" field, which is supposedly a "private" demangler field.
To avoid such problems in the future, this commit switches those
places to use "fill_comp" instead, and eliminates the "make_empty"
function.

gdb/ChangeLog:
2017-03-27  Pedro Alves  <palves@redhat.com>

	* cp-name-parser.y (make_empty): Delete.
	(demangler_special, nested_name, ptr_operator, array_indicator)
	(direct_declarator, declarator_1): Use fill_comp instead of
	make_empty.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbserver: xtensa: add call0 support
@ 2017-03-27 21:13 sergiodj+buildbot
  2017-06-26  9:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-27 21:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a09b50a463ad005946849540da136b5cbe6237b ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: 1a09b50a463ad005946849540da136b5cbe6237b

gdbserver: xtensa: add call0 support

Correctly handle a0- registers on requests from remote gdb. This fixes

  'Register 1 is not available'

and subsequent assertion in the remote gdb connecting to the gdbserver:

  'findvar.c:291: internal-error: value_of_register_lazy:
    Assertion `frame_id_p(get_frame_id (frame))' failed.'

The register structure is the same for windowed and call0 ABIs because
currently linux kernel internally requires windowed registers, so they
are always present.

gdb/gdbserver/
2017-03-27  Max Filippov  <jcmvbkbc@gmail.com>

	* linux-xtensa-low.c (xtensa_fill_gregset): Call collect_register
	for all registers in a0_regnum..a0_regnum + C0_NREGS range.
	(xtensa_store_gregset): Call supply_register for all registers in
	a0_regnum..a0_regnum + C0_NREGS range.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbserver: xtensa: support THREADPTR register
@ 2017-03-27 22:23 sergiodj+buildbot
  2017-06-28 14:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-27 22:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a12e714b775ce025444af15dcfbd5a420363ad53 ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: a12e714b775ce025444af15dcfbd5a420363ad53

gdbserver: xtensa: support THREADPTR register

Provide aceess to the THREADPTR register to remote gdb.

gdb/gdbserver/
2017-03-27  Max Filippov  <jcmvbkbc@gmail.com>

	* linux-xtensa-low.c (regnum::R_THREADPTR): New enum member.
	(xtensa_fill_gregset): Call collect_register_by_name for
	threadptr register.
	(xtensa_store_gregset): Call supply_register_by_name for
	threadptr register.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc: Align internal regnums with architectural regnums
@ 2017-03-28 18:58 sergiodj+buildbot
  2017-06-29 11:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-28 18:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 296ec4fa2afb14abc400fa0109d7288eb958c544 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: 296ec4fa2afb14abc400fa0109d7288eb958c544

arc: Align internal regnums with architectural regnums

Add ARC_LIMM_REGNUM to arc_regnum enumeration and assign a number 62 to it.
This ensures that for core registers internal register numbers in this enum are
the same as architectural numbers.  This allows to use internal register
numbers in the contexts where architectural number is implied, for example when
disassembling instruction during prologue analysis.

gdb/ChangeLog:

yyyy-mm-dd  Anton Kolesov  <anton.kolesov@synopsys.com>

	* arc-tdep.c (core_v2_register_names, core_arcompact_register_names)
	Add "limm" and "reserved".
	(arc_cannot_fetch_register, arc_cannot_store_register): Add
	ARC_RESERVED_REGNUM and ARC_LIMM_REGNUM.
	* arc-tdep.h (arc_regnum): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] arc: Add prologue analysis
@ 2017-03-28 20:37 sergiodj+buildbot
  2017-07-01 22:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-03-28 20:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe5f7374bef8f23ffa0fe0dee0f9b05e0a218a29 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: fe5f7374bef8f23ffa0fe0dee0f9b05e0a218a29

arc: Add prologue analysis

Add a prologue analysis that recognizes all instructions that may happen in
compiler-generated prologue, including various stores, core register moves,
subtraction and ENTER_S instruction that does a lot of prologue actions through
microcode.

Testcases cover various prologue scenarios, including instructions that are
spread across multiple 16-bit encodings (for example there are 7 encodings of
store instruction).

gdb/ChangeLog:

yyyy-mm-dd  Anton Kolesov  <anton.kolesov@synopsys.com>

	* arc-tdep.c (arc_frame_cache): Add support for prologue analysis.
	(arc_skip_prologue): Likewise.
	(arc_make_frame_cache): Likewise.
	(arc_pv_get_operand): New function.
	(arc_is_in_prologue): Likewise.
	(arc_analyze_prologue): Likewise.
	(arc_print_frame_cache): Likewise.
	(MAX_PROLOGUE_LENGTH): New constant.

gdb/doc/ChangeLog:

yyyy-mm-dd  Anton Kolesov  <anton.kolesov@synopsys.com>

	* gdb.texinfo (Synopsys ARC): Document "set debug arc 2".

gdb/testsuite/ChangeLog:

yyyy-mm-dd  Anton Kolesov  <anton.kolesov@synopsys.com>

	* gdb.arch/arc-analyze-prologue.S: New file.
	* gdb.arch/arc-analyze-prologue.exp: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] IA16 support
@ 2017-04-03 16:30 sergiodj+buildbot
  2017-07-15 19:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-03 16:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f5f29cada3c06c9c26f4da5994951effee7d6f7 ***

Author: Andrew Jenner <andrew@codesourcery.com>
Branch: master
Commit: 2f5f29cada3c06c9c26f4da5994951effee7d6f7

IA16 support

       * config.sub: Handle ia16 in $basic_machine.

       bfd/
       * config.bfd: Handle ia16.

       gas/
       * configure.tgt: Handle ia16.

       ld/
       * configure.tgt: Handle ia16.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix null pointer dereferences when using a link built with clang.
@ 2017-04-04 10:51 sergiodj+buildbot
  2017-07-17 19:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-04 10:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad32986fdf9da1c8748e47b8b45100398223dba8 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: ad32986fdf9da1c8748e47b8b45100398223dba8

Fix null pointer dereferences when using a link built with clang.

	PR binutils/21342
	* elflink.c (_bfd_elf_define_linkage_sym): Prevent null pointer
	dereference.
	(bfd_elf_final_link): Only initialize the extended symbol index
	section if there are extended symbol tables to list.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] remote.c: Use ptid_t instead of struct ptid
@ 2017-04-04 14:49 sergiodj+buildbot
  2017-07-18 16:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-04 14:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d62a8ae2dd0fbb6235f4e8f2fb61b83fe4ba1d90 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: d62a8ae2dd0fbb6235f4e8f2fb61b83fe4ba1d90

remote.c: Use ptid_t instead of struct ptid

It's the only place in the codebase that uses "struct ptid", so change
it to ptid_t for consistency.

gdb/ChangeLog:

	* remote.c (set_general_thread, set_continue_thread): Use ptid_t
	instead of struct ptid.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] dwarf2read.c: Make dir_index and file_name_index strong typedefs
@ 2017-04-04 20:48 sergiodj+buildbot
  2017-07-24 16:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-04 20:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ecfb656c37b982479d8eb07f240b434772d98fd6 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ecfb656c37b982479d8eb07f240b434772d98fd6

dwarf2read.c: Make dir_index and file_name_index strong typedefs

This should help catch mistakes related to mixing the 1-based DWARF
indexes with 0-based std::vector indexes, since the new types do not
implicitly convert to anything.

The change in read_formatted_entries relates to the fact that doing
the seemingly simpler:

 -	      uintp = &fe.dir_index;
 +	      uintp = (unsigned int *) &fe.dir_index;

would be undefined C/C++.  So to address that, I made the function
extract the form before assigning to the file_entry.  It felt natural
to use gdb::optional for "do I have this value", and this is what
motivated the previous patch that added the missing observer methods
to gdb::optional.

gdb/ChangeLog:
2017-04-04  Pedro Alves  <palves@redhat.com>

	* common/underlying.h: New file.
	* dwarf2read.c: Include "common/gdb_optional.h" and
	"common/underlying.h".
	(dir_index, file_name_index): New types.
	(file_entry): Use them.
	(file_entry::include): Use to_underlying.
	(line_header::add_file_name): Use dir_index.
	(read_formatted_entries): Use gdb::optional.  Read form before
	writting to file_entry.
	(dwarf_decode_line_header): Use dir_index.
	(lnp_state_machine::current_file): Use to_underlying.
	(lnp_state_machine::file): Change type to file_name_index.
	(dwarf_record_line): Use to_underlying.
	(init_lnp_state_machine): Use file_name_index.
	(dwarf_decode_lines_1): Use dir_index and file_name_index.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Make sect_offset and cu_offset strong typedefs instead of structs
@ 2017-04-04 21:06 sergiodj+buildbot
  2017-07-25 13:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-04 21:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c5417255690af00751c7d506172459afe856894 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 9c5417255690af00751c7d506172459afe856894

Make sect_offset and cu_offset strong typedefs instead of structs

A while ago, back when GDB was a C program, the sect_offset and
cu_offset types were made structs in order to prevent incorrect mixing
of those offsets.  Now that we require C++11, we can make them
integers again, while keeping the safety, by exploiting "enum class".
We can add a bit more safety, even, by defining operators that the
types _should_ support, helping making the suspicious uses stand out
more.

Getting at the underlying type is done with the new to_underlying
function added by the previous patch, which also helps better spot
where do we need to step out of the safety net.  Mostly, that's around
parsing the DWARF, and when we print the offset for complaint/debug
purposes.  But there are other occasional uses.

Since we have to define the sect_offset/cu_offset types in a header
anyway, I went ahead and generalized/library-fied the idea of "offset"
types, making it trivial to add more such types if we find a use.  See
common/offset-type.h and the DEFINE_OFFSET_TYPE macro.

I needed a couple generaly-useful preprocessor bits (e.g., yet another
CONCAT implementation), so I started a new common/preprocessor.h file.

I included units tests covering the "offset" types API.  These are
mostly compile-time tests, using SFINAE to check that expressions that
shouldn't compile (e.g., comparing unrelated offset types) really are
invalid and would fail to compile.  This same idea appeared in my
pending enum-flags revamp from a few months ago (though this version
is a bit further modernized compared to what I had posted), and I plan
on reusing the "check valid expression" bits added here in that
series, so I went ahead and defined the CHECK_VALID_EXPR macro in its
own header -- common/valid-expr.h.  I think that's nicer regardless.

I was borderline between calling the new types "offset" types, or
"index" types, BTW.  I stuck with "offset" simply because that's what
we're already calling them, mostly.

gdb/ChangeLog:
2017-04-04  Pedro Alves  <palves@redhat.com>

	* Makefile.in (SUBDIR_UNITTESTS_SRCS): Add
	unittests/offset-type-selftests.c.
	(SUBDIR_UNITTESTS_OBS): Add offset-type-selftests.o.
	* common/offset-type.h: New file.
	* common/preprocessor.h: New file.
	* common/traits.h: New file.
	* common/valid-expr.h: New file.
	* dwarf2expr.c: Include "common/underlying.h".  Adjust to use
	sect_offset and cu_offset strong typedefs throughout.
	* dwarf2expr.h: Adjust to use sect_offset and cu_offset strong
	typedefs throughout.
	* dwarf2loc.c: Include "common/underlying.h".  Adjust to use
	sect_offset and cu_offset strong typedefs throughout.
	* dwarf2read.c: Adjust to use sect_offset and cu_offset strong
	typedefs throughout.
	* gdbtypes.h: Include "common/offset-type.h".
	(cu_offset): Now an offset type (strong typedef) instead of a
	struct.
	(sect_offset): Likewise.
	(union call_site_parameter_u): Rename "param_offset" field to
	"param_cu_off".
	* unittests/offset-type-selftests.c: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove support for FreeBSD/alpha.
@ 2017-04-04 23:00 sergiodj+buildbot
  2017-07-28  1:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-04 23:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e1a8bef60db2f524c5eb1d27be22cfa9ff82a84 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 1e1a8bef60db2f524c5eb1d27be22cfa9ff82a84

Remove support for FreeBSD/alpha.

FreeBSD last shipped a release for Alpha (6.3) in 2008.
This also removes support for GNU/kFreeBSD on Alpha.

gdb/ChangeLog:

	* Makefile.in (ALL_64_TARGET_OBS): Remove alpha-fbsd-tdep.o.
	(ALLDEPFILES): Remove alpha-fbsd-tdep.c
	* NEWS: Mention that support for FreeBSD/alpha was removed.
	* alpha-fbsd-tdep.c: Delete file.
	* config/alpha/fbsd.mh: Delete file.
	* configure.host: Delete alpha*-*-freebsd* and
	alpha*-*-kfreebsd*-gnu.
	* configure.tgt: Delete alpha*-*-freebsd* and
	alpha*-*-kfreebsd*-gnu.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Initialize gdb::optional empty payload to quiet false -Wmaybe-uninitialized warnings
@ 2017-04-05  1:01 sergiodj+buildbot
  2017-07-29 17:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-05  1:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c053b65441eb70ac78a514fabc3431b857a30d2e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c053b65441eb70ac78a514fabc3431b857a30d2e

Initialize gdb::optional empty payload to quiet false -Wmaybe-uninitialized warnings

Commit ecfb656c37b982 ("dwarf2read.c: Make dir_index and
file_name_index strong typedefs") added a use of gdb::optional that
triggers bogus -Wmaybe-uninitialized warnings:

GCC trunk is complaining like this:

  ../../binutils-gdb/gdb/dwarf2read.c: In function void read_formatted_entries(bfd*, const gdb_byte**, line_header*, const comp_unit_head*, void (*)(line_header*, const char*, dir_index, unsigned int, unsigned int)):
  ../../binutils-gdb/gdb/dwarf2read.c:17779:65: error: fe.file_entry::length may be used uninitialized in this function [-Werror=maybe-uninitialized]
	 callback (lh, fe.name, fe.d_index, fe.mod_time, fe.length);
								   ^
  ../../binutils-gdb/gdb/dwarf2read.c:17779:65: error: *((void*)& fe +8) may be used uninitialized in this function [-Werror=maybe-uninitialized]
  ../../binutils-gdb/gdb/dwarf2read.c:17779:65: error: fe.file_entry::mod_time may be used uninitialized in this function [-Werror=maybe-uninitialized]
  ../../binutils-gdb/gdb/dwarf2read.c:17779:65: error: fe.file_entry::name may be used uninitialized in this function [-Werror=maybe-uninitialized]

While some older GCCs are complaining like this:

  ../../binutils-gdb/gdb/dwarf2read.c: In function void read_formatted_entries(bfd*, const gdb_byte**, line_header*, const comp_unit_head*, void (*)(line_header*, const char*, dir_index, unsigned int, unsigned int)):
  ../../binutils-gdb/gdb/dwarf2read.c:17779:65: error: uint may be used uninitialized in this function [-Werror=maybe-uninitialized]
	 callback (lh, fe.name, fe.d_index, fe.mod_time, fe.length);

Looking around the web, I see that boost's optional implementation
triggers this kind of issue often too.  See:

  http://www.boost.org/doc/libs/1_63_0/libs/optional/doc/html/boost_optional/tutorial/gotchas/false_positive_with__wmaybe_uninitialized.html

I noticed that replacing the gdb::optional uses with real C++17
std::optional uses against GCC 7/trunk makes the warnings go away.
Looking at the implementation, AFAICS, libstdc++ always initializes
its "empty" union payload member (_M_empty, which is defined as an
empty class, like ours).  I.e., all payload types have this ctor:

    struct _Optional_payload.....
    {
      constexpr _Optional_payload()
	: _M_empty() {}

The constexpr makes a diference too.  Without it, GCC7 still warns.

So I'm applying the same treatment to our gdb::optional.

gdb/ChangeLog:
2017-04-05  Pedro Alves  <palves@redhat.com>

	* common/gdb_optional.h (optional::optional): Make constexpr and
	initialize m_dummy.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix racy test in gdb.threads/thread-specific-bp.exp
@ 2017-04-05 14:11 sergiodj+buildbot
  2017-08-01  8:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-05 14:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 55a98976756cb2df83ac8f8e9799331fbcc4f669 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 55a98976756cb2df83ac8f8e9799331fbcc4f669

Fix racy test in gdb.threads/thread-specific-bp.exp

I see the following test fail from time to time, due to the racy test
in gdb.threads/thread-specific-bp.exp.

continue -a^M
Continuing.^M
^M
Thread 1 "thread-specific" hit Breakpoint 4, end () at binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:29^M
29      }^M
(gdb) [Thread 0x40322460 (LWP 12950) exited]^M
Thread-specific breakpoint 3 deleted - thread 2 no longer in the thread list.^M
FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)

This patch changes gdb_test to gdb_test_multiple to match prompt only
instead of both prompt and anchor.

gdb/testsuite:

2017-04-05  Yao Qi  <yao.qi@linaro.org>

	* gdb.threads/thread-specific-bp.exp (check_thread_specific_breakpoint):
	Use gdb_test_multiple, and don't match anchor.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Use frame_unwind_register_value in frame_unwind_register_unsigned
@ 2017-04-05 15:20 sergiodj+buildbot
  2017-08-02  4:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-05 15:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2cad08ea7dbc96103da9957da6973f9d0dbc33a8 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 2cad08ea7dbc96103da9957da6973f9d0dbc33a8

Use frame_unwind_register_value in frame_unwind_register_unsigned

gdb:

2017-04-05  Yao Qi  <yao.qi@linaro.org>

	* frame.c (frame_unwind_register_unsigned): Call
	frame_unwind_register_value.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] -Wwrite-strings: Constify shell_escape and plug make_command leak
@ 2017-04-05 20:34 sergiodj+buildbot
  2017-08-07  7:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-05 20:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be47f9e8180d7275b0e2b26998472e99be9a2d7b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: be47f9e8180d7275b0e2b26998472e99be9a2d7b

-Wwrite-strings: Constify shell_escape and plug make_command leak

gdb/ChangeLog:
2017-04-05  Pedro Alves	 <palves@redhat.com>

	* cli/cli-cmds.c (shell_escape): Constify 'arg' parameter.
	(shell_command): New function.
	(make_command): Use std::string.
	(init_cli_cmds): Register shell_command instead of shell_escape.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] -Wwrite-strings: Don't initialize string command variables to empty string
@ 2017-04-05 21:07 sergiodj+buildbot
  2017-08-06 10:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-05 21:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bde6261aed330cd8d108c387bfe659a6171525dd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: bde6261aed330cd8d108c387bfe659a6171525dd

-Wwrite-strings: Don't initialize string command variables to empty string

-Wwrite-strings flags these initializations as requiring a cast.
However, these variables are command variables, and as such point to
heap-allocated memory.  The initial allocation is always done when the
corresponding command is registered.  E.g.,:

    dprintf_function = xstrdup ("printf");
    add_setshow_string_cmd ("dprintf-function", class_support,
			    &dprintf_function, _("\
  Set the function to use for dynamic printf"), _("\
  Show the function to use for dynamic printf"), NULL,
			    update_dprintf_commands, NULL,
			    &setlist, &showlist);

That's why we never reach a bogus attempt to free these string
literals.

So, just drop the incorrect initializations.

gdb/ChangeLog:
2017-04-05  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (dprintf_function, dprintf_channel): Don't initialize.
	* tracepoint.c (default_collect): Don't initialize.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] -Wwrite-strings: More fix-old-Python-API wrappers
@ 2017-04-06  0:12 sergiodj+buildbot
  2017-08-14  6:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-06  0:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d75997912d77497fd395fde222513436a7df046 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4d75997912d77497fd395fde222513436a7df046

-Wwrite-strings: More fix-old-Python-API wrappers

When building against Python 2.7, -Wwrite-strings flags several cases
of passing a string literal to Python functions that expect a "char
*".  This commit addresses the issue like we already handle several
other similar cases -- wrap the Python API with our own fixed
version that adds the necessary constification.

gdb/ChangeLog:
2017-04-05  Pedro Alves  <palves@redhat.com>

	* python/python-internal.h (gdb_PyObject_CallMethod)
	(gdb_PyErr_NewException, gdb_PySys_GetObject, gdb_PySys_SetPath):
	New functions.
	(GDB_PYSYS_SETPATH_CHAR, PyObject_CallMethod, PyErr_NewException)
	(PySys_GetObject, PySys_SetPath): New macros.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] -Wwrite-strings: execute_command calls with string literals
@ 2017-04-06  1:31 sergiodj+buildbot
  2017-08-17  6:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-06  1:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b2eba3dcc6b41f17180e1aee29ed133f942c733 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 9b2eba3dcc6b41f17180e1aee29ed133f942c733

-Wwrite-strings: execute_command calls with string literals

This is ugly, but it's just making the uglyness explicit.

All these places would better be calling some API function directly
instead of going through execute_command & friends...

gdb/ChangeLog:
2017-04-05  Pedro Alves  <palves@redhat.com>

	* event-top.c (command_line_handler): Add cast to execute_command
	call.
	* record-btrace.c (cmd_record_btrace_bts_start)
	(cmd_record_btrace_pt_start, cmd_record_btrace_start)
	(cmd_record_btrace_start): Add cast to execute_command call.
	* record-full.c (record_full_goto_insn):
	* record.c (record_start, record_stop): Add cast to
	execute_command_to_string calls.
	(cmd_record_start): Add cast to execute_command calls.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] ptid_{lwp,tid}_p: Remove unnecessary checks
@ 2017-04-06  4:14 sergiodj+buildbot
  2017-08-22 19:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-06  4:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e9868d4e0c8e45505876901d22c021dd36972a8 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 4e9868d4e0c8e45505876901d22c021dd36972a8

ptid_{lwp,tid}_p: Remove unnecessary checks

The calls to ptid_equal in ptid_lwp_p and ptid_tid_p that compare the
argument to minus_one_ptid and null_ptid are not necessary.  The calls
in question are:

   if (ptid_equal (minus_one_ptid, ptid)
       || ptid_equal (null_ptid, ptid))
     return 0;

minus_one_ptid is { .pid = -1, .lwp = 0, .tid = 0 }
null_ptid is { .pid = 0, .lwp = 0, .tid = 0 }

If the ptid argument is either of them, the statements

  return (ptid_get_lwp (ptid) != 0);

and

  return (ptid_get_tid (ptid) != 0);

will yield the same result (0/false).

gdb/ChangeLog:

	* common/ptid.c (ptid_lwp_p, ptid_tid_p): Remove comparison with
	minus_one_ptid and null_ptid.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] -Wwrite-strings: More Solaris
@ 2017-04-06 12:43 sergiodj+buildbot
  2017-08-20 12:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-06 12:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 995816ba55d952b2823d2ead66495c5cad6dfe58 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 995816ba55d952b2823d2ead66495c5cad6dfe58

-Wwrite-strings: More Solaris

Some obvious constifications found by attempting to build 64-bit GDB
on Solaris 11.

gdb/ChangeLog:
2017-04-05  Pedro Alves  <palves@redhat.com>

	* proc-api.c (struct trans): Constify.
	(procfs_note): Constify.
	* proc-events.c (struct trans, syscall_table):
	* proc-flags.c (struct trans): Constify.
	* proc-utils.h (procfs_note): Constify.
	* proc-why.c (struct trans): Constify.
	* procfs.c (dead_procinfo, find_syscall, proc_warn, proc_error)
	(procfs_detach): Constify.
	* sol-thread.c (struct string_map): Constify.
	(td_err_string, td_state_string): Constify.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Regen SRC-POTFILES.in
@ 2017-04-06 16:16 sergiodj+buildbot
  2017-08-23 17:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-04-06 16:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86abf93a3a56ccdf1c5f15b841ee9d6a0516a2cf ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 86abf93a3a56ccdf1c5f15b841ee9d6a0516a2cf

Regen SRC-POTFILES.in

Missed when elf-properties.c was added.

	* po/SRC-POTFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove unused function set_inferior_target_data
@ 2017-08-24 21:53 sergiodj+buildbot
  2017-09-01  4:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-24 21:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a160cc4628aa125959dc65983d805500fc58512c ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: a160cc4628aa125959dc65983d805500fc58512c

Remove unused function set_inferior_target_data

The inferior (thread) target data is always set through add_thread.

gdb/gdbserver/ChangeLog:

	* inferiors.c (set_inferior_target_data): Remove.
	* inferiors.h (set_inferior_target_data): Remove.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdbserver: Rename some functions, thread -> inferior
@ 2017-08-25  9:18 sergiodj+buildbot
  2017-09-02  2:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-25  9:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6afd337d1a1a789b71d77b157529c08250eb9093 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 6afd337d1a1a789b71d77b157529c08250eb9093

gdbserver: Rename some functions, thread -> inferior

These functions apply to thread, and not inferiors (in the gdbserver
sense, the abstraction for threads and processes, as in
inferior_list).  Therefore, it would make more sense if these functions
were named with "thread" rather than "inferior".

gdb/gdbserver/ChangeLog:

	* inferiors.h (inferior_target_data): Rename to ...
	(thread_target_data): ... this.
	(inferior_regcache_data): Rename to ...
	(thread_regcache_data): ... this.
	(set_inferior_regcache_data): Rename to ...
	(set_thread_regcache_data): ... this.
	* inferiors.c (inferior_target_data): Rename to ...
	(thread_target_data): ... this.
	(inferior_regcache_data): Rename to ...
	(thread_regcache_data): ... this.
	(set_inferior_regcache_data): Rename to ...
	(set_thread_regcache_data): ... this.
	(free_one_thread): Update.
	* linux-low.h (get_thread_lwp): Update.
	* regcache.c (get_thread_regcache): Update.
	(regcache_invalidate_thread): Update.
	(free_register_cache_thread): Update.
	* win32-i386-low.c (update_debug_registers_callback): Update.
	(win32_get_current_dr): Update.
	* win32-low.c (thread_rec): Update.
	(delete_thread_info): Update.
	(continue_one_thread): Update.
	(suspend_one_thread): Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Remove redundant "symbol" in comments
@ 2017-08-26  0:39 sergiodj+buildbot
  2017-09-02 22:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-26  0:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fdda9d6a4c3520f4787d96c4ae293783fe6262a ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 5fdda9d6a4c3520f4787d96c4ae293783fe6262a

x86: Remove redundant "symbol" in comments

	* elf32-i386.c (elf_i386_link_hash_entry): Remove redundant
	"symbol" in comments.
	* elf64-x86-64.c (elf_x86_64_link_hash_entry): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <74081948353b117fcbe870fc3cc9ebe0f18fdcf8@gdb-build>]
* [binutils-gdb] PowerPC TPREL reloc handling
@ 2017-08-26 11:54 sergiodj+buildbot
  2017-09-04 16:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-26 11:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c8bbca5e670b5ea44b61ff30c5c7fcec47ee405 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 7c8bbca5e670b5ea44b61ff30c5c7fcec47ee405

PowerPC TPREL reloc handling

Tidy how these are handled in PIEs.

	* elf32-ppc.c (must_be_dyn_reloc): Use bfd_link_dll.  Comment.
	(ppc_elf_check_relocs): Only set DF_STATIC_TLS in shared libs.
	(ppc_elf_relocate_section): Comment fix.
	* elf64-ppc.c (must_be_dyn_reloc): Use bfd_link_dll.  Comment.
	(ppc64_elf_check_relocs): Only set DF_STATIC_TLS in shared libs.
	Support dynamic relocs for TPREL16 when non-pic too.
	(dec_dynrel_count): Adjust TPREL16 handling as per check_relocs.
	(ppc64_elf_relocate_section): Support dynamic relocs for TPREL16
	when non-pic too.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
[parent not found: <f1902523c9b7941775a2c64af89de0f111b8924c@gdb-build>]
* [binutils-gdb] x86: Initialize def_protected
@ 2017-08-27 14:46 sergiodj+buildbot
  2017-09-06  6:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-27 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 596dc58f33e20bd2784459dc0931e92922465444 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 596dc58f33e20bd2784459dc0931e92922465444

x86: Initialize def_protected

	* elf32-i386.c (elf_i386_link_hash_newfunc): Initialize
	def_protected.
	* elf64-x86-64.c (elf_x86_64_link_hash_newfunc): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Check for valid PLT section size
@ 2017-08-28 18:53 sergiodj+buildbot
  2017-09-07  7:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-28 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 90efb6422939ca031804266fba669f77c22a274a ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 90efb6422939ca031804266fba669f77c22a274a

x86: Check for valid PLT section size

Update x86 get_synthetic_symtab to check for valid PLT section size
before examining PLT section contents.

	PR binutils/22018
	* elf32-i386.c (elf_i386_get_synthetic_symtab): Check for valid
	PLT section size.
	* elf64-x86-64.c (elf_x86_64_get_synthetic_symtab): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove unused _bfd_elf_ifunc_get_synthetic_symtab
@ 2017-08-28 23:21 sergiodj+buildbot
  2017-09-10 16:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-28 23:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fb0a7677827aea3e7ca1fdb2dfd1ccbdf6c2f71 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 0fb0a7677827aea3e7ca1fdb2dfd1ccbdf6c2f71

Remove unused _bfd_elf_ifunc_get_synthetic_symtab

Since _bfd_elf_ifunc_get_synthetic_symtab is no longer called by x86
get_synthetic_symtab, it is now unused.  This patch removes it.

	* elf-bfd.h (_bfd_elf_ifunc_get_synthetic_symtab): Removed.
	* elf-ifunc.c (_bfd_elf_ifunc_get_synthetic_symtab): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix simulation of MSP430's open system call.
@ 2017-08-29 13:35 sergiodj+buildbot
  2017-09-11 21:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-29 13:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3819af136deb7ba6bc2058d7848cf80b33dbe51c ***

Author: Jozef Lawrynowicz <jozef.l@somniumtech.com>
Branch: master
Commit: 3819af136deb7ba6bc2058d7848cf80b33dbe51c

Fix simulation of MSP430's open system call.

	* sim/msp430/msp430-sim.c (maybe_perform_syscall): Fix passing of
	arguments for variadic syscall "open".


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Check valid PLT sections before checking dynamic relocations
@ 2017-08-29 18:16 sergiodj+buildbot
  2017-09-12 19:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-29 18:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37c0b6ee65941d54fa8064c21b39f97fdc318156 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 37c0b6ee65941d54fa8064c21b39f97fdc318156

x86: Check valid PLT sections before checking dynamic relocations

Update x86 get_synthetic_symtab to check valid PLT sections before
checking dynamic relocations and free invalid PLT section contents.

	* elf32-i386.c (elf_i386_get_synthetic_symtab): Check valid PLT
	sections before checking dynamic relocations and free invalid
	PLT section contents.
	* elf64-x86-64.c (elf_x86_64_get_synthetic_symtab): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Simplify bad return in get_synthetic_symtab
@ 2017-08-29 18:56 sergiodj+buildbot
  2017-09-14  1:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-29 18:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 823cb06774ad6a2aee0afcf6f011c3a134f25747 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 823cb06774ad6a2aee0afcf6f011c3a134f25747

x86: Simplify bad return in get_synthetic_symtab

	* elf32-i386.c (elf_i386_get_synthetic_symtab): Simplify bad
	return.
	* elf64-x86-64.c (elf_x86_64_get_synthetic_symtab): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Re-indent elf32-i386.c/elf64-x86-64.c
@ 2017-08-29 22:11 sergiodj+buildbot
  2017-09-15 12:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-29 22:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f0f0847e23a57d4e95c2c639e803e6f51914efc ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 5f0f0847e23a57d4e95c2c639e803e6f51914efc

x86: Re-indent elf32-i386.c/elf64-x86-64.c

	* elf32-i386.c (elf_i386_pie_finish_undefweak_symbol):
	Re-indent.
	* elf64-x86-64.c (elf_x86_64_finish_local_dynamic_symbol):
	Likewise.
	(elf_x86_64_pie_finish_undefweak_symbol): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PowerPC64 __tls_get_addr sequence optimization
@ 2017-08-30 11:36 sergiodj+buildbot
  2017-09-17 23:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-30 11:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b9f04fe0dfe64bc6224e7bb96378607f17da7446 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: b9f04fe0dfe64bc6224e7bb96378607f17da7446

PowerPC64 __tls_get_addr sequence optimization

There isn't a good reason for ld.bfd to behave differently from gold
in the code generated by TLS GD/LD to LE optimization.

bfd/
	* elf64-ppc.c (ppc64_elf_relocate_section): When optimizing
	__tls_get_addr call sequences to LE, don't move the addi down
	to the nop.  Replace the bl with addi and leave the nop alone.
ld/
	* testsuite/ld-powerpc/tls.d: Update.
	* testsuite/ld-powerpc/tlsexe.d: Update.
	* testsuite/ld-powerpc/tlsexetoc.d: Update.
	* testsuite/ld-powerpc/tlsld.d: Update.
	* testsuite/ld-powerpc/tlsmark.d: Update.
	* testsuite/ld-powerpc/tlsopt4.d: Update.
	* testsuite/ld-powerpc/tlstoc.d: Update.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PowerPC TPREL16_HA/LO reloc optimization
@ 2017-08-30 12:05 sergiodj+buildbot
  2017-09-18 11:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-30 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a23f96e919ba91587d077b1d399246dde4002dd ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 9a23f96e919ba91587d077b1d399246dde4002dd

PowerPC TPREL16_HA/LO reloc optimization

In the TLS GD/LD to LE optimization, ld replaces a sequence like

 addi 3,2,x@got@tlsgd		R_PPC64_GOT_TLSGD16	x
 bl __tls_get_addr(x@tlsgd)	R_PPC64_TLSGD		x
				R_PPC64_REL24		__tls_get_addr
 nop

with

 addis 3,13,x@tprel@ha		R_PPC64_TPREL16_HA	x
 addi 3,3,x@tprel@l		R_PPC64_TPREL16_LO	x
 nop

When the tprel offset is small, this can be further optimized to

 nop
 addi 3,13,x@tprel
 nop

bfd/
	* elf64-ppc.c (struct ppc_link_hash_table): Add do_tls_opt.
	(ppc64_elf_tls_optimize): Set it.
	(ppc64_elf_relocate_section): Nop addis on TPREL16_HA, and convert
	insn on TPREL16_LO and TPREL16_LO_DS relocs to use r13 when
	addis would add zero.
	* elf32-ppc.c (struct ppc_elf_link_hash_table): Add do_tls_opt.
	(ppc_elf_tls_optimize): Set it.
	(ppc_elf_relocate_section): Nop addis on TPREL16_HA, and convert
	insn on TPREL16_LO relocs to use r2 when addis would add zero.
gold/
	* powerpc.cc (Target_powerpc::Relocate::relocate): Nop addis on
	TPREL16_HA, and convert insn on TPREL16_LO and TPREL16_LO_DS
	relocs to use r2/r13 when addis would add zero.
ld/
	* testsuite/ld-powerpc/tls.s: Add calls with tls markers.
	* testsuite/ld-powerpc/tls32.s: Likewise.
	* testsuite/ld-powerpc/powerpc.exp: Run tls marker tests.
	* testsuite/ld-powerpc/tls.d: Adjust for TPREL16_HA/LO optimization.
	* testsuite/ld-powerpc/tlsexe.d: Likewise.
	* testsuite/ld-powerpc/tlsexetoc.d: Likewise.
	* testsuite/ld-powerpc/tlsld.d: Likewise.
	* testsuite/ld-powerpc/tlsmark.d: Likewise.
	* testsuite/ld-powerpc/tlsopt4.d: Likewise.
	* testsuite/ld-powerpc/tlstoc.d: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove elf_x86_64_next_tls_desc_index/elf_x86_64_srelplt2
@ 2017-08-30 12:51 sergiodj+buildbot
  2017-09-19  7:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-30 12:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f2425c4c8fdaa7822555bbb61468b46d4e4af20 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 0f2425c4c8fdaa7822555bbb61468b46d4e4af20

Remove elf_x86_64_next_tls_desc_index/elf_x86_64_srelplt2

They are unused.

	* elf64-x86-64.c (elf_x86_64_next_tls_desc_index): Removed.
	(elf_x86_64_srelplt2): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] MIPS/BFD: Correct microMIPS cross-mode BAL to JALX relaxation
@ 2017-08-30 15:38 sergiodj+buildbot
  2017-09-20 23:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-30 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70e65ca8e5d1fc984d58f6137c290e807fe772a5 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 70e65ca8e5d1fc984d58f6137c290e807fe772a5

MIPS/BFD: Correct microMIPS cross-mode BAL to JALX relaxation

Fix a bug in commit a6ebf6169a1b ("MIPS: Convert cross-mode BAL to
JALX") and in BFD linker relaxation correct the microMIPS interpretation
of the branch offset, which is supposed to be shifted by 1 bit, rather
than 2 as in the regular MIPS case.

	bfd/
	* elfxx-mips.c (mips_elf_perform_relocation): Correct microMIPS
	branch offset interpretation.

	gas/
	* testsuite/gas/mips/branch-addend-micromips.d: New test.
	* testsuite/gas/mips/branch-addend-micromips-n32.d: New test.
	* testsuite/gas/mips/branch-addend-micromips-n64.d: New test.
	* testsuite/gas/mips/branch-addend-micromips.s: New test source.
	* testsuite/gas/mips/mips.exp: Run the new tests.

	ld/
	* testsuite/ld-mips-elf/bal-jalx-addend-micromips.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-addend-micromips-n32.d: New
	test.
	* testsuite/ld-mips-elf/bal-jalx-addend-micromips-n64.d: New
	test.
	* testsuite/ld-mips-elf/bal-jalx-local-micromips.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-local-micromips-n32.d: New
	test.
	* testsuite/ld-mips-elf/bal-jalx-local-micromips-n64.d: New
	test.
	* testsuite/ld-mips-elf/bal-jalx-pic-micromips.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-pic-micromips-n32.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-pic-micromips-n64.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-pic-ignore-micromips.d: New
	test.
	* testsuite/ld-mips-elf/bal-jalx-pic-ignore-micromips-n32.d: New
	test.
	* testsuite/ld-mips-elf/bal-jalx-pic-ignore-micromips-n64.d: New
	test.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Add _bfd_x86_elf_link_hash_table_create
@ 2017-08-30 16:30 sergiodj+buildbot
  2017-09-21 19:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-30 16:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 765e526c75506a7d9644bc7c137ac1923fdb1369 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 765e526c75506a7d9644bc7c137ac1923fdb1369

x86: Add _bfd_x86_elf_link_hash_table_create

Share _bfd_x86_elf_link_hash_table_create in elf32-i386.c and
elf64-x86-64.c by:

1. Replace elf_i386_lazy_plt_layout, elf_i386_non_lazy_plt_layout,
elf_i386_plt_layout, elf_x86_64_lazy_plt_layout,
elf_x86_64_non_lazy_plt_layout and elf_x86_64_plt_layout with
elf_x86_lazy_plt_layout, elf_x86_non_lazy_plt_layout and
elf_x86_plt_layout.
2. Move plt, lazy_plt, non_lazy_plt, srelplt2 and next_tls_desc_index
from elf_i386_link_hash_table to elf_x86_link_hash_table.
3. Remove elf_i386_link_hash_table and elf_x86_64_link_hash_table.

	* elf32-i386.c (ELF_DYNAMIC_INTERPRETER): Removed.
	(elf_i386_lazy_plt_layout): Likewise.
	(elf_i386_non_lazy_plt_layout): Likewise.
	(elf_i386_plt_layout): Likewise.
	(elf_i386_link_hash_table): Likewise.
	(elf_i386_next_tls_desc_index): Likewise.
	(elf_i386_srelplt2): Likewise.
	(elf_i386_plt): Likewise.
	(elf_i386_lazy_plt): Likewise.
	(elf_i386_non_lazy_plt): Likewise.
	(elf_i386_link_hash_table_create): Likewise.
	(bfd_elf32_bfd_link_hash_table_create): Likewise.
	(elf_i386_lazy_plt): Updated.
	(elf_i386_non_lazy_plt): Likewise.
	(elf_i386_lazy_ibt_plt): Likewise.
	(elf_i386_non_lazy_ibt_plt): Likewise.
	(elf_i386_allocate_dynrelocs): Likewise.
	(elf_i386_size_dynamic_sections): Likewise.
	(elf_i386_relocate_section): Likewise.
	(elf_i386_finish_dynamic_symbol): Likewise.
	(elf_i386_finish_dynamic_sections): Likewise.
	(elf_i386_get_synthetic_symtab): Likewise.
	(elf_i386_link_setup_gnu_properties): Likewise.
	(elf_i386_nacl_plt): Likewise.
	* elf64-x86-64.c (ABI_64_P): Removed.
	(ELF64_DYNAMIC_INTERPRETER): Likewise.
	(ELF32_DYNAMIC_INTERPRETER): Likewise.
	(elf_x86_64_lazy_plt_layout): Likewise.
	(elf_x86_64_non_lazy_plt_layout): Likewise.
	(elf_x86_64_plt_layout): Likewise.
	(elf_x86_64_link_hash_table): Likewise.
	(elf_x86_64_plt): Likewise.
	(elf_x86_64_lazy_plt): Likewise.
	(elf_x86_64_non_lazy_plt): Likewise.
	(elf_x86_64_link_hash_table_create): Likewise.
	(bfd_elf64_bfd_link_hash_table_create): Likewise.
	(bfd_elf32_bfd_link_hash_table_create): Likewise.
	(elf_x86_64_lazy_plt): Updated.
	(elf_x86_64_non_lazy_plt): Likewise.
	(elf_x86_64_lazy_bnd_plt): Likewise.
	(elf_x86_64_non_lazy_bnd_plt): Likewise.
	(elf_x86_64_lazy_ibt_plt): Likewise.
	(elf_x32_lazy_ibt_plt): Likewise.
	(elf_x86_64_non_lazy_ibt_plt): Likewise.
	(elf_x32_non_lazy_ibt_plt): Likewise.
	(elf_x86_64_allocate_dynrelocs): Likewise.
	(elf_x86_64_size_dynamic_sections): Likewise.
	(elf_x86_64_relocate_section): Likewise.
	(elf_x86_64_finish_dynamic_symbol): Likewise.
	(elf_x86_64_finish_dynamic_sections): Likewise.
	(elf_x86_64_get_synthetic_symtab): Likewise.
	(elf_x86_64_link_setup_gnu_properties): Likewise.
	(elf_x86_64_nacl_plt): Likewise.
	* elfxx-x86.c: Include "objalloc.h", "elf/i386.h" and
	"elf/x86-64.h".
	(ELF32_DYNAMIC_INTERPRETER): New.
	(ELF64_DYNAMIC_INTERPRETER): Likewise.
	(ELFX32_DYNAMIC_INTERPRETER): Likewise.
	(_bfd_x86_elf_link_hash_table_create): Likewise.
	(_bfd_x86_elf_link_hash_table_free): Renamed to ...
	(elf_x86_link_hash_table_free): This.  Make it static.
	* elfxx-x86.h: Don't include "objalloc.h".
	(ABI_64_P): New.
	(elf_x86_lazy_plt_layout): Likewise.
	(elf_x86_non_lazy_plt_layout): Likewise.
	(elf_x86_plt_layout): Likewise.
	(_bfd_x86_elf_link_hash_table_create): Likewise.
	(bfd_elf64_bfd_link_hash_table_create): Likewise.
	(bfd_elf32_bfd_link_hash_table_create): Likewise.
	(elf_x86_link_hash_table): Add plt, lazy_plt, non_lazy_plt,
	srelplt2 and next_tls_desc_index.
	(_bfd_x86_elf_link_hash_table_free): Removed.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Add _bfd_x86_elf_get_synthetic_symtab
@ 2017-08-30 19:49 sergiodj+buildbot
  2017-09-23 17:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-30 19:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f493882dab762fb49ecb8685c18a85edfab5e6d3 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: f493882dab762fb49ecb8685c18a85edfab5e6d3

x86: Add _bfd_x86_elf_get_synthetic_symtab

Move the common codes in elf_i386_get_synthetic_symtab and
elf_x86_64_get_synthetic_symtab to _bfd_x86_elf_get_synthetic_symtab.

	* elf32-i386.c (elf_i386_plt_type): Removed.
	(elf_i386_plt): Likewise.
	(elf_i386_get_synthetic_symtab): Updated.   Call
	_bfd_x86_elf_get_synthetic_symtab.
	* elf64-x86-64.c (elf_x86_64_plt_type): Removed.
	(elf_x86_64_plt): Likewise.
	(elf_x86_64_get_synthetic_symtab): Updated.  Call
	_bfd_x86_elf_get_synthetic_symtab.
	* elfxx-x86.c (elf_i386_get_plt_got_vma): New function.
	(elf_x86_64_get_plt_got_vma): Likewise.
	(elf_i386_valid_plt_reloc_p): Likewise.
	(elf_x86_64_valid_plt_reloc_p): Likewise.
	(_bfd_x86_elf_get_synthetic_symtab): Likewise.
	* elfxx-x86.h (elf_x86_plt_type): New.
	(elf_x86_plt): Likewise.
	(_bfd_x86_elf_get_synthetic_symtab): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] bfd_close_all_done calling _close_and_cleanup
@ 2017-08-31  1:26 sergiodj+buildbot
  2017-09-24  9:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-31  1:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e234de6be5cc96286e0efb90e8d9fce51239e901 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: e234de6be5cc96286e0efb90e8d9fce51239e901

bfd_close_all_done calling _close_and_cleanup

elf64_vms_close_and_cleanup calls bfd_get_size, which calls
iovec->bstat.  cache_bstat ends up adding the bfd to the cache lru
list, negating the bfd_cache_close call in bfd_close_all_done.  So
there is a dangling pointer into the freed and then reused bfd.  Thus,
bfd_cache_close must be called after _close_and_cleanup, or better,
via iovec->bclose.

	PR binutils/22032
	* opncls.c (bfd_close_all_done): Don't call bfd_cache_close
	before _close_and_cleanup.  Call iovec->bclose after.
	(bfd_close): Remove code common to, and call, bfd_close_all_done.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] FT32: Permit R_FT32_18 overflow
@ 2017-08-31  3:19 sergiodj+buildbot
  2017-09-25  6:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-31  3:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef32532f22be7e98c25480449fbc7a80d1030e1e ***

Author: James Bowman <jamesb@excamera.com>
Branch: master
Commit: ef32532f22be7e98c25480449fbc7a80d1030e1e

FT32: Permit R_FT32_18 overflow

The howto for R_FT32_18 was using complain_overflow_signed. But some
valid address calculations exceed the range of this reloc.  Changing it
to complain_overflow_dont allows them.

bfd/ChangeLog:

	* elf32-ft32.c (ft32_elf_howto_table): Use
	complain_overflow_dont for R_FT32_18.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add elf64.lo together with elfxx-x86.lo for 64-bit BFD
@ 2017-08-31  4:05 sergiodj+buildbot
  2017-09-27  4:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-31  4:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3321e42bf2b5819b76ca36e8964fe7cf9a8ae9a2 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 3321e42bf2b5819b76ca36e8964fe7cf9a8ae9a2

Add elf64.lo together with elfxx-x86.lo for 64-bit BFD

Since elfxx-x86.lo needs elf64.lo with 64-bit BFD, add elf64.lo together
with elfxx-x86.lo to bfd_backends for 64-bit BFD.

	* configure.ac (bfd_backends): Add elf64.lo together with
	elfxx-x86.lo for 64-bit BFD.
	* configure: Regenerated.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR22048, Incorrect .eh_frame section in libc.so
@ 2017-08-31  4:27 sergiodj+buildbot
  2017-09-27 23:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-31  4:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af471f828cc74d65b50a7531ba2c69522266cfe9 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: af471f828cc74d65b50a7531ba2c69522266cfe9

PR22048, Incorrect .eh_frame section in libc.so

	PR 21441
	PR 22048
	* elflink.c (bfd_elf_discard_info): Don't pad embedded zero
	terminators.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix buffer read overrun by ensuring that DWARF sections containing strings always end in a NUL byte.
@ 2017-08-31 16:43 sergiodj+buildbot
  2017-10-02 13:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-31 16:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e4f2723003859dc6b33ca0dadbc4a7659ebf1643 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: e4f2723003859dc6b33ca0dadbc4a7659ebf1643

Fix buffer read overrun by ensuring that DWARF sections containing strings always end in a NUL byte.

	PR 22047
	* dwarf2.c (read_section): If necessary add a terminating NUL byte
	to dwarf string sections.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Implement the ability to set/unset environment variables to GDBserver when starting the inferior
@ 2017-08-31 22:00 sergiodj+buildbot
  2017-10-03 10:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-08-31 22:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a2dde4a321d2f7bd2ded9a558b9ae92892de0e2 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 0a2dde4a321d2f7bd2ded9a558b9ae92892de0e2

Implement the ability to set/unset environment variables to GDBserver when starting the inferior

This patch implements the ability to set/unset environment variables
on the remote target, mimicking what GDB already offers to the user.
There are two features present here: user-set and user-unset
environment variables.

User-set environment variables are only the variables that are
explicitly set by the user, using the 'set environment' command.  This
means that variables that were already present in the environment when
starting GDB/GDBserver are not transmitted/considered by this feature.

User-unset environment variables are variables that are explicitly
unset by the user, using the 'unset environment' command.

The idea behind this patch is to store user-set and user-unset
environment variables in two separate sets, both part of gdb_environ.
Then, when extended_remote_create_inferior is preparing to start the
inferior, it will iterate over the two sets and set/unset variables
accordingly.  Three new packets are introduced:

- QEnvironmentHexEncoded, which is used to set environment variables,
  and contains an hex-encoded string in the format "VAR=VALUE" (VALUE
  can be empty if the user set a variable with a null value, by doing
  'set environment VAR=').

- QEnvironmentUnset, which is used to unset environment variables, and
  contains an hex-encoded string in the format "VAR".

- QEnvironmentReset, which is always the first packet to be
  transmitted, and is used to reset the environment, i.e., discard any
  changes made by the user on previous runs.

The QEnvironmentHexEncoded packet is inspired on LLDB's extensions to
the RSP.  Details about it can be seen here:

  <https://raw.githubusercontent.com/llvm-mirror/lldb/master/docs/lldb-gdb-remote.txt>

I decided not to implement the QEnvironment packet because it is
considered deprecated by LLDB.  This packet, on LLDB, serves the same
purpose of QEnvironmentHexEncoded, but sends the information using a
plain text, non-hex-encoded string.

The other two packets are new.

This patch also includes updates to the documentation, testsuite, and
unit tests, without introducing regressions.

gdb/ChangeLog:
2017-08-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* NEWS (Changes since GDB 8.0): Add entry mentioning new support
	for setting/unsetting environment variables on the remote target.
	(New remote packets): Add entries for QEnvironmentHexEncoded,
	QEnvironmentUnset and QEnvironmentReset.
	* common/environ.c (gdb_environ::operator=): Extend method to
	handle m_user_set_env_list and m_user_unset_env_list.
	(gdb_environ::clear): Likewise.
	(match_var_in_string): Change type of first parameter from 'char
	*' to 'const char *'.
	(gdb_environ::set): Extend method to handle
	m_user_set_env_list and m_user_unset_env_list.
	(gdb_environ::unset): Likewise.
	(gdb_environ::clear_user_set_env): New method.
	(gdb_environ::user_set_envp): Likewise.
	(gdb_environ::user_unset_envp): Likewise.
	* common/environ.h (gdb_environ): Handle m_user_set_env_list and
	m_user_unset_env_list on move constructor/assignment.
	(unset): Add new default parameter 'update_unset_list = true'.
	(clear_user_set_env): New method.
	(user_set_envp): Likewise.
	(user_unset_envp): Likewise.
	(m_user_set_env_list): New std::set.
	(m_user_unset_env_list): Likewise.
	* common/rsp-low.c (hex2str): New function.
	(bin2hex): New overload for bin2hex function.
	* common/rsp-low.c (hex2str): New prototype.
	(str2hex): New overload prototype.
	* remote.c: Include "environ.h". Add QEnvironmentHexEncoded,
	QEnvironmentUnset and QEnvironmentReset.
	(remote_protocol_features): Add QEnvironmentHexEncoded,
	QEnvironmentUnset and QEnvironmentReset packets.
	(send_environment_packet): New function.
	(extended_remote_environment_support): Likewise.
	(extended_remote_create_inferior): Call
	extended_remote_environment_support.
	(_initialize_remote): Add QEnvironmentHexEncoded,
	QEnvironmentUnset and QEnvironmentReset packet configs.
	* unittests/environ-selftests.c (gdb_selftest_env_var):
	New variable.
	(test_vector_initialization): New function.
	(test_init_from_host_environ): Likewise.
	(test_reinit_from_host_environ): Likewise.
	(test_set_A_unset_B_unset_A_cannot_find_A_can_find_B):
	Likewise.
	(test_unset_set_empty_vector): Likewise.
	(test_vector_clear): Likewise.
	(test_std_move): Likewise.
	(test_move_constructor):
	(test_self_move): Likewise.
	(test_set_unset_reset): Likewise.
	(run_tests): Rewrite in terms of the functions above.

gdb/gdbserver/ChangeLog:
2017-08-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* server.c (handle_general_set): Handle QEnvironmentHexEncoded,
	QEnvironmentUnset and QEnvironmentReset packets.
	(handle_query): Inform remote that QEnvironmentHexEncoded,
	QEnvironmentUnset and QEnvironmentReset are supported.

gdb/doc/ChangeLog:
2017-08-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gdb.texinfo (set environment): Add @anchor.  Explain that
	environment variables set by the user are sent to GDBserver.
	(unset environment): Likewise, but for unsetting variables.
	(Connecting) <Remote Packet>: Add "environment-hex-encoded",
	"QEnvironmentHexEncoded", "environment-unset", "QEnvironmentUnset",
	"environment-reset" and "QEnvironmentReset" to the table.
	(Remote Protocol) <QEnvironmentHexEncoded, QEnvironmentUnset,
	QEnvironmentReset>: New item, explaining the packet.

gdb/testsuite/ChangeLog:
2017-08-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gdb.base/share-env-with-gdbserver.c: New file.
	* gdb.base/share-env-with-gdbserver.exp: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR gdb/22046: Fix T-stopped detach regression on old Linux kernels
@ 2017-09-01  5:02 sergiodj+buildbot
  2017-10-04  6:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-09-01  5:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c811d30d12b6f7c6c6f4ce6d03408d987154548 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 5c811d30d12b6f7c6c6f4ce6d03408d987154548

PR gdb/22046: Fix T-stopped detach regression on old Linux kernels

On <=RHEL6 hosts Fedora/RHEL GDB started to 'kill -STOP' all processes it
detached.  Even those not originally T-stopped.  This is a Fedora-specific
patch which is based on upstream GDB's PROC_STATE_STOPPED state.

I believe (I did not verify) this patch did regress it:
commit d617208bb06bd461b52ce041d89f7127e3044762
Author: Pedro Alves <palves@redhat.com>
Date:   Mon Jul 25 12:42:17 2016 +0100
    linux-procfs: Introduce enum proc_state

As originally there was strstr() but now there is strcmp() and so the missing
trailing '\n' no longer matches.

The Bug was found by Michal Kolar.

Reproducibility:
$ gdb -p $PID
(gdb) quit
$ ...

Actual results:
===
RHEL6.9 x86_64 # scl enable devtoolset-7 bash
RHEL6.9 x86_64 # which gdb
/opt/rh/devtoolset-7/root/usr/bin/gdb
RHEL6.9 x86_64 # ./testcase.sh
24737 pts/0    S+     0:00 /bin/sleep 4
24737 pts/0    T+     0:00 /bin/sleep 4
RHEL6.9 x86_64 #
===

Expected results:
===
RHEL6.9 x86_64 # which gdb
/usr/bin/gdb
RHEL6.9 x86_64 # ./testcase.sh
24708 pts/0    S+     0:00 /bin/sleep 4
24708 pts/0    S+     0:00 /bin/sleep 4
./testcase.sh: line 20: kill: (24708) - No such process
RHEL6.9 x86_64 #
===

gdb/ChangeLog
2017-09-01  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR gdb/22046
	* nat/linux-procfs.c (parse_proc_status_state): Fix PROC_STATE_STOPPED
	detection.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix -list-thread-groups --available logic and add test
@ 2017-10-04 16:48 sergiodj+buildbot
  2017-10-04 23:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-04 16:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c71c1059f876fcca9809f7b6372b721ddb83635 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 4c71c1059f876fcca9809f7b6372b721ddb83635

Fix -list-thread-groups --available logic and add test

New in v3:

- Replace use_gdb_stub with can_spawn_for_attach.
- Call kill_wait_spawned_process on spawn_ids.

Commit

  Use std::set in mi-main.c
  52f9abe4c739f42cc5f80b2629276493ac6306f9

changed the logic of the "-list-thread-groups --available" by mistake
when a pid is passed.  It prints all the processes except the one
specified by the given pid.  The correct behavior is to only print the
process corresponding to that pid.  this patch fixes that and adds a test.

gdb/ChangeLog:

	* mi/mi-main.c (list_available_thread_groups): Reverse filter logic.

gdb/testsuite/ChangeLog:

	* gdb.mi/list-thread-groups-available.exp: New file.
	* gdb.mi/list-thread-groups-available.c: New file.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Redesign mock environment for gdbarch selftests
@ 2017-10-04 17:39 sergiodj+buildbot
  2017-10-05 19:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-04 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 55b11ddf16b97b9c50ed480bc9da8b3e1c6c4198 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 55b11ddf16b97b9c50ed480bc9da8b3e1c6c4198

Redesign mock environment for gdbarch selftests

A following patch will remove this hack from within regcache's
implementation:

  struct regcache *
  get_thread_arch_regcache (ptid_t ptid, struct gdbarch *gdbarch)
  {
    struct address_space *aspace;

    /* For the benefit of "maint print registers" & co when debugging an
       executable, allow dumping the regcache even when there is no
       thread selected (target_thread_address_space internal-errors if
       no address space is found).  Note that normal user commands will
       fail higher up on the call stack due to no
       target_has_registers.  */
    aspace = (ptid_equal (null_ptid, ptid)
	      ? NULL
	      : target_thread_address_space (ptid));

i.e., it'll no longer be possible to try to build a regcache for
null_ptid.  That change alone would regress the gdbarch self tests
though, causing this:

  (gdb) maintenance selftest
  [...]
  Running selftest register_to_value.
  src/gdb/inferior.c:309: internal-error: inferior* find_inferior_pid(int): Assertion `pid != 0' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) FAIL: gdb.gdb/unittest.exp: maintenance selftest (GDB internal error)

The problem is that the way the mocking environment for those unit
tests is written is a bit fragile: it creates a special purpose
regcache (and sentinel's frame), using whatever is the current
inferior_ptid (usually null_ptid), and assumes get_current_regcache
will find that in the regcache::current_regcache list.

This commit changes the way the mock environment is created.  It
eliminates the special regcache and frame and instead creates a fuller
mock environment, with a custom mock target_ops, and then a mock
inferior and thread "running" on that target.

If there's already a running target when you type "maint selftest",
then we error out, instead of pushing a new target on top of the
existing one (and thus killing the debug session).  This results in:

  (gdb) maint selftest
  (...)
  Self test failed: arch i386: target already pushed
  Self test failed: arch i386:x86-64: target already pushed
  Self test failed: arch i386:x64-32: target already pushed
  Self test failed: arch i8086: target already pushed
  Self test failed: arch i386:intel: target already pushed
  Self test failed: arch i386:x86-64:intel: target already pushed
  Self test failed: arch i386:x64-32:intel: target already pushed
  Self test failed: arch i386:nacl: target already pushed
  Self test failed: arch i386:x86-64:nacl: target already pushed
  Self test failed: arch i386:x64-32:nacl: target already pushed
  Self test failed: self-test failed at /home/pedro/gdb/mygit/src/gdb/selftest-arch.c:86
  (...)
  Ran 19 unit tests, 1 failed

I think that's OK, because self tests are really meant to be run from
a clean state right after GDB is started.  I'm adding that erroring
out just as safe measure just in case someone types "maint selftest"
on the command line while already debugging something (as I've done
it).

(In my multi-target branch, where this patch originated from, we don't
actually need to error out, because there each inferior has its own
target stack).

Also, note that the current code was doing:

 current_inferior()->gdbarch = gdbarch;

without taking care to restore the previous gdbarch.  This means that
GDB's state was being left inconsistent after running the self tests,
further supporting the point that there's probably not much
expectation that mixing "maint selftests" and regular debugging in the
same GDB invocation really works.  This patch fixes that, regardless.

gdb/ChangeLog:
2017-10-04  Pedro Alves  <palves@redhat.com>

	* frame.c (create_test_frame): Delete.
	* frame.h (create_test_frame): Delete.
	* gdbarch-selftests.c: Include gdbthread.h and target.h.
	(class regcache_test): Delete.
	(test_target_has_registers, test_target_has_stack)
	(test_target_has_memory, test_target_prepare_to_store)
	(test_target_store_registers): New functions.
	(test_target_ops): New class.
	(register_to_value_test): Error out if there's already a
	process_stratum (or higher) target pushed.  Create a fuller mock
	environment, with mock target_ops, inferior, address space, thread
	and inferior_ptid.
	* progspace.c (struct address_space): Move to ...
	* progspace.h (struct address_space): ... here.
	* regcache.h (regcache::~regcache, regcache::raw_write)
	[GDB_SELF_TEST]: No longer virtual.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix "Remote 'g' packet reply is too long" problems with multiple inferiors
@ 2017-10-04 17:39 sergiodj+buildbot
  2017-10-11 11:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-04 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5cd63fda035d4ba949e6478406162c4673b3c9ef ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5cd63fda035d4ba949e6478406162c4673b3c9ef

Fix "Remote 'g' packet reply is too long" problems with multiple inferiors

When debugging two inferiors (or more) against gdbserver, and the
inferiors have different architectures, such as e.g., on x86_64
GNU/Linux and one inferior is 64-bit while the other is 32-bit, then
GDB can get confused with the different architectures in a couple
spots.

In both cases I ran into, GDB incorrectly ended up using the
architecture of whatever happens to be the selected inferior instead
of the architecture of some other given inferior:

#1 - When parsing the expedited registers in stop replies.

#2 - In the default implementation of the target_thread_architecture
     target method.

These resulted in instances of the infamous "Remote 'g' packet reply
is too long" error.  For example, with the test added in this commit,
we get:

~~~
  Continuing.
  Remote 'g' packet reply is too long (expected 440 bytes, got 816 bytes): ad064000000000000[snip]
  (gdb) FAIL: gdb.multi/multi-arch.exp: inf1 event with inf2 selected: continue to hello_loop

  c
  Continuing.
  Truncated register 50 in remote 'g' packet
  (gdb) PASS: gdb.multi/multi-arch.exp: inf2 event with inf1 selected: c
~~~

This commit fixes that.

gdb/ChangeLog:
2017-10-04  Pedro Alves  <palves@redhat.com>

	* remote.c (get_remote_arch_state): New 'gdbarch' parameter.  Use
	it instead of target_gdbarch.
	(get_remote_state, get_remote_packet_size): Adjust
	get_remote_arch_state calls, passing down target_gdbarch
	explicitly.
	(packet_reg_from_regnum, packet_reg_from_pnum): New parameter
	'gdbarch' and use it instead of target_gdbarch.
	(get_memory_packet_size): Adjust get_remote_arch_state calls,
	passing down target_gdbarch explicitly.
	(struct stop_reply) <arch>: New field.
	(remote_parse_stop_reply): Use the stopped thread's architecture,
	not the current inferior's.  Save the architecture in the
	stop_reply.
	(process_stop_reply): Use the stop reply's architecture.
	(process_g_packet, remote_fetch_registers)
	(remote_prepare_to_store, store_registers_using_G)
	(remote_store_registers): Adjust get_remote_arch_state calls,
	using the regcache's architecture.
	(remote_get_trace_status): Adjust get_remote_arch_state calls,
	passing down target_gdbarch explicitly.
	* spu-multiarch.c (spu_thread_architecture): Defer to the target
	beneath instead of calling target_gdbarch.
	* target.c (default_thread_architecture): Use the specified
	inferior's architecture, instead of the current inferior's
	architecture (via target_gdbarch).

gdb/testsuite/ChangeLog:
2017-10-04  Pedro Alves  <palves@redhat.com>

	* gdb.multi/hangout.c: Include <unistd.h>.
	(hangout_loop): New function.
	(main): Call alarm.  Call hangout_loop in a loop.
	* gdb.multi/hello.c: Include <unistd.h>.
	(hello_loop): New function.
	(main): Call alarm.  Call hangout_loop in a loop.
	* gdb.multi/multi-arch.exp: Test running to a breakpoint one
	inferior with the other selected.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR21167, relocation sections not included in groups
@ 2017-10-04 23:08 sergiodj+buildbot
  2017-10-12  8:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-04 23:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db4677b8bd90b49f826807352c6c3c7eb0d57814 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: db4677b8bd90b49f826807352c6c3c7eb0d57814

PR21167, relocation sections not included in groups

This fixes a wart I've known about for years, but haven't done
anything about because BFD treats relocation sections as an adjunct to
the section they relocate.  SHF_GROUP on the section thus implicitly
applies to its relocation section(s), but it is an error that the
reloc sections aren't part of the group.

Like many patches to gas, this wasn't as straightforward as it could
be due to a number of backends, i386, cr16 and others, removing relocs
in tc_get_reloc rather than marking them as "done" earlier in
md_apply_reloc.  So it isn't possible for the group support to
reliably detect the presence of relocs by looking at fixups earlier
than write_relocs.  However the group support needs to create
signature symbols, and that must be done before the symbol table is
frozen, before write_relocs.  So split off the group sizing from
elf_adjust_symtab and put it in elf_frob_file_after_relocs.

bfd/
	PR 21167
	* elf.c (_bfd_elf_setup_sections): Don't trim reloc sections from
	groups.
	(_bfd_elf_init_reloc_shdr): Pass sec_hdr, use it to copy SHF_GROUP
	flag from section.
	(elf_fake_sections): Adjust calls.  Exit immediately on failure.
	(bfd_elf_set_group_contents): Add associated reloc section indices
	to group contents
gas/
	PR 21167
	* config/obj-elf.c (struct group_list): Delete elt_count.
	(groups): New static.
	(build_group_lists): Don't count elements.
	(elf_adjust_symtab): Use groups rather than auto list.  Set up
	pointer from group member to SHT_GROUP section.  Don't size
	SHT_GROUP section or clean up here..
	(elf_frob_file_after_relocs): ..do so here instead.
	* testsuite/gas/arc/jli-1.d,
	* testsuite/gas/elf/groupautob.d,
	* testsuite/gas/mips/compact-eh-eb-2.d,
	* testsuite/gas/mips/compact-eh-eb-5.d,
	* testsuite/gas/mips/compact-eh-el-2.d,
	* testsuite/gas/mips/compact-eh-el-5.d: Adjust.
ld/
	PR 21167
	* testsuite/ld-elf/group9b.d: Adjust for relocs included in group.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] bfd_error_on_input is for archives
@ 2017-10-05  1:09 sergiodj+buildbot
  2017-10-13 15:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05  1:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8c6716e57eb991ba6ceb07011045d626652aaf01 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 8c6716e57eb991ba6ceb07011045d626652aaf01

bfd_error_on_input is for archives

	* elflink.c (elf_link_input_bfd): Correct ctor/dtor in init_array/
	fini_array error value.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] bfd_set_input_error
@ 2017-10-05  1:42 sergiodj+buildbot
  2017-10-14 12:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05  1:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ca7de3746be7484aa5affceafa1ad2e1d789381 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2ca7de3746be7484aa5affceafa1ad2e1d789381

bfd_set_input_error

A downside to the 2017-10-04 PR22245 fix is that bfd_set_error can now
silently accept invalid errors if/when someone passes the a value of
the wrong enumeration type, which previously would be caught by the
-Wenum-conversion warning.

	PR 22245
	* bfd.c (bfd_set_error): Revert 2017-10-04 change.  Remove
	ellipsis parameter.  Split out bfd_error_on_input code to..
	(bfd_set_input_error): .. New function.
	* archive.c (_bfd_write_archive_contents): Use bfd_set_input_error.
	* vms-lib.c (_bfd_vms_lib_write_archive_contents): Likewise.
	* bfd-in2.h: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Update my email address.
@ 2017-10-05  4:45 sergiodj+buildbot
  2017-10-15  8:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05  4:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c91933e9e33654c7b8973cb449b93f5152afcbcb ***

Author: Tristan Gingold <tgingold@free.fr>
Branch: master
Commit: c91933e9e33654c7b8973cb449b93f5152afcbcb

Update my email address.

Also refer to global maintainers for branch release approval.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] tile: Dump dynamic relocation info to the map file
@ 2017-10-05 13:02 sergiodj+buildbot
  2017-10-16  9:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05 13:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 007873f54e41eaef2f7a89b8adbb63a563d98b65 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 007873f54e41eaef2f7a89b8adbb63a563d98b65

tile: Dump dynamic relocation info to the map file

Dump dynamic relocation info to the map file when generating dynamic
relocation in read-only section relocations if -Map is used.

	* elf32-tilepro.c (readonly_dynrelocs): Dump dynamic relocation
	in read-only section with minfo.
	(tilepro_elf_size_dynamic_sections): Likewise.
	* elfxx-tilegx.c (readonly_dynrelocs): Likewise.
	(tilegx_elf_size_dynamic_sections): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Handle the NT_ARM_VFP core dump note on FreeBSD.
@ 2017-10-05 17:00 sergiodj+buildbot
  2017-10-18  3:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05 17:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d5be5d6b8b4412e65bc037472aa2e727c25ccf5 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 6d5be5d6b8b4412e65bc037472aa2e727c25ccf5

Handle the NT_ARM_VFP core dump note on FreeBSD.

bfd/ChangeLog:

	* elf.c (elfcore_grok_freebsd_note): Handle NT_ARM_VFP.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add a signal frame unwinder for FreeBSD/mipsn32.
@ 2017-10-05 17:00 sergiodj+buildbot
  2017-10-19  2:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05 17:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a80a647180bf92692e0f01efe7b323afe7d317c9 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: a80a647180bf92692e0f01efe7b323afe7d317c9

Add a signal frame unwinder for FreeBSD/mipsn32.

The N32 signal frame uses an identical layout to N64, so reuse the N64
handler.  The N32 signal trampoline does use one different instruction
relative to N64, so a separate tramp_frame is required.

gdb/ChangeLog:

	* mips-fbsd-tdep.c (MIPS_INST_ADDIU_A0_SP_N32): Define.
	(mipsn32_fbsd_sigframe): Define.
	(mips_fbsd_init_abi): Install mipsn32_fbsd_sigframe unwinder
	for FreeBSD/mipsn32.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Handle FreeBSD-specific AT_EHDRFLAGS and AT_HWCAP auxiliary vector types.
@ 2017-10-05 17:00 sergiodj+buildbot
  2017-10-17  6:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05 17:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12c4bd7f53e9cefcf7c3a7f8cbf9e552526cb963 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 12c4bd7f53e9cefcf7c3a7f8cbf9e552526cb963

Handle FreeBSD-specific AT_EHDRFLAGS and AT_HWCAP auxiliary vector types.

FreeBSD recently added two additional ELF auxiliary vectors.  FreeBSD's
AT_HWCAP uses a different number compared to AT_HWCAP on Linux as the
numerical value was already in use for a different vector on FreeBSD.

include/ChangeLog:

	* elf/common.h (AT_FREEBSD_EHDRFLAGS, AT_FREEBSD_HWCAP): Define.

gdb/ChangeLog:

	* fbsd-tdep.c (fbsd_print_auxv_entry): Handle AT_EHDRFLAGS and
	AT_HWCAP.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Remove unused "union agent_val" from ax.h
@ 2017-10-05 17:18 sergiodj+buildbot
  2017-10-21 20:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d13b8493cbd2891b5886e6176d468eb63c73606a ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: d13b8493cbd2891b5886e6176d468eb63c73606a

Remove unused "union agent_val" from ax.h

The ax.h header file contains a use of DOUBLEST in the type "union agent_val".

However, that type is never used anywhere, so it can be simply removed.

gdb/ChangeLog:
2017-10-05  Ulrich Weigand  <uweigand@de.ibm.com>

	* ax.h: Do not include "doublest.h".
	(union agent_val): Remove.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Clean up some DFP interfaces
@ 2017-10-05 17:18 sergiodj+buildbot
  2017-10-20 21:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b4b2f160d288b85a1379d24fd0f4de19062f3fd ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 3b4b2f160d288b85a1379d24fd0f4de19062f3fd

Clean up some DFP interfaces

This cleans up a number of interfaces in dfp.c / dfp.h.  Specifically:

- The decimal_from_string / decimal_to_string routines are C++-ified
  to operate on std::string instead of character buffers.  In the
  decimal_from_string, the boolean return value now actually is bool
  instead of an int.

- The decimal_from_integral and decimal_from_doublest routines take
  an struct value as input.  This is not really appropriate at the low
  level the DFP routines sit, so this replaced them with new routines
  decimal_from_longest / decimal_from_ulongest / decimal_from_doublest
  that operate on contents instead.

- To mirror the decimal_from_[u]longest, a new decimal_to_longest
  routine is added as well, which can be used in unpack_long to
  avoid an unnecessary conversion via DOUBLEST.

Note that the decimal_from_longest / decimal_from_ulongest routines
are actually more powerful than decimal_from_integral: the old routine
would only accept integer *types* of at most four bytes size, while
the new routines accept all integer *values* that fit in an [u]int32_t,
no matter which type they came from.  The DFP tests are updated to
allow for this larger range of integers that can be converted.

gdb/ChangeLog:
2017-10-05  Ulrich Weigand  <uweigand@de.ibm.com>

	* dfp.h (MAX_DECIMAL_STRING): Move to dfp.c.
	(decimal_to_string): Return std::string object.
	(decimal_from_string): Accept std::string object.  Return bool.
	(decimal_from_integral, decimal_from_doublest): Remove.
	(decimal_from_longest): Add prototype.
	(decimal_from_ulongest): Likewise.
	(decimal_to_longest): Likewise.
	(decimal_from_doublest): Likewise.
	* dfp.c: Do not include "gdbtypes.h" or "value.h".
	(MAX_DECIMAL_STRING): Move here.
	(decimal_to_string): Return std::string object.
	(decimal_from_string): Accept std::string object.  Return bool.
	(decimal_from_integral): Remove, replace by ...
	(decimal_from_longest, decimal_from_ulongest): ... these new functions.
	(decimal_to_longest): New function.
	(decimal_from_floating): Remove, replace by ...
	(decimal_from_doublest): ... this new function.
	(decimal_to_doublest): Update to new decimal_to_string interface.

	* value.c (unpack_long): Use decimal_to_longest.
	* valops.c (value_cast): Use decimal_from_doublest instead of
	decimal_from_floating.  Use decimal_from_[u]longest isntead of
	decimal_from_integral.
	* valarith.c (value_args_as_decimal): Likewise.
	* valprint.c (print_decimal_floating): Update to new
	decimal_to_string interface.
	* printcmd.c (printf_decfloat): Likewise.
	* c-exp.y (parse_number): Update to new decimal_from_string interface.

gdb/testsuite/ChangeLog:
2017-10-05  Ulrich Weigand  <uweigand@de.ibm.com>

	* gdb.base/dfp-exprs.exp: Update tests to larger range of supported
	integer-to-dfp conversion.
	* gdb.base/dfp-test.exp: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Clean up includes of doublest.h and floatformat.h
@ 2017-10-05 17:18 sergiodj+buildbot
  2017-10-20  0:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1841ee5d0300cf00022c8aadfe16725c5e86fe1d ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 1841ee5d0300cf00022c8aadfe16725c5e86fe1d

Clean up includes of doublest.h and floatformat.h

As a first small step to getting rid of doublest.h, this patch removes the
include of "floatformat.h" in "doublest.h".  This is actually not needed
for the file itself.  A few source files now need to include "floatformat.h"
directly, since they got it indirectly via "doublest.h" and still need it.

In reviewing which files need it, I found a number of files that include
"floatformat.h" directly without actually needing it at all.  Similarly,
a number of files include "doublest.h" without needing it.  I've also
removed those unnecessary include statements.

gdb/ChangeLog:
2017-10-05  Ulrich Weigand  <uweigand@de.ibm.com>

	* doublest.h: Do not include "floatformat.h".  Remove stale comments.
	* gdbtypes.c: Include "floatformat.h".
	* value.c: Likewise.
	* m68k-tdep.c: Likewise.

	* findvar.c: Do not include "floatformat.h".
	* amd64-darwin-tdep.c: Likewise.
	* arm-linux-tdep.c: Likewise.
	* i386-darwin-tdep.c: Likewise.
	* i387-tdep.c: Likewise.
	* m68k-linux-tdep.c: Likewise.
	* mep-tdep.c: Likewise.
	* mips-tdep.c: Likewise.
	* nios2-tdep.c: Likewise.
	* s390-linux-tdep.c: Likewise.
	* sparc-obsd-tdep.c: Likewise.
	* sparc-tdep.c: Likewise.
	* sparc64-tdep.c: Likewise.
	* spu-tdep.c: Likewise.
	* tic6x-tdep.c: Likewise.
	* tilegx-tdep.c: Likewise.
	* vax-tdep.c: Likewise.
	* xstormy16-tdep.c: Likewise.
	* xtensa-tdep.c: Likewise.

	* top.c: Do not include "doublest.h".
	* aarch64-tdep.c: Likewise.
	* alpha-tdep.c: Likewise.
	* arm-linux-tdep.c: Likewise.
	* m68k-linux-tdep.c: Likewise.
	* tilegx-tdep.c: Likewise.
	* xstormy16-tdep.c: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix fork-related regressions on GNU/Linux
@ 2017-10-05 17:35 sergiodj+buildbot
  2017-10-22 17:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-05 17:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2fd9d7ca17539ce983862b25e0abc27cfb706189 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2fd9d7ca17539ce983862b25e0abc27cfb706189

Fix fork-related regressions on GNU/Linux

Commit 5cd63fda035d ("Fix "Remote 'g' packet reply is too long"
problems with multiple inferiors") caused a number of regressions on
native GNU/Linux, all related to follow-fork support.  E.g.:

  src/gdb/target.c:3141: internal-error: gdbarch* default_thread_architecture(target_ops*, ptid_t): Assertion `inf != NULL' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n)
  Resyncing due to internal error.
  FAIL: gdb.base/catch-signal-fork.exp: got SIGHUP after fork (GDB internal error)

This commit fixes it.

gdb/ChangeLog:
2017-10-05  Pedro Alves  <palves@redhat.com>

	* linux-nat.c (linux_child_follow_fork): When following the parent
	and detaching the child, consult the parent thread's architecture
	instead of the child's.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Add TLS_TRANSITION_IE_TO_LE_P
@ 2017-10-06  7:18 sergiodj+buildbot
  2017-10-24  9:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06  7:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51537393bd939e79f6e9291629fb65a17e6f19da ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 51537393bd939e79f6e9291629fb65a17e6f19da

x86: Add TLS_TRANSITION_IE_TO_LE_P

Add TLS_TRANSITION_IE_TO_LE_P which returns TRUE if TLS IE->LE transition
is OK.

	* elfxx-x86.h (TLS_TRANSITION_IE_TO_LE_P): New.
	* elf32-i386.c (elf_i386_tls_transition): Use it.
	* elf64-x86-64.c (elf_x86_64_tls_transition): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Add NEED_DYNAMIC_RELOCATION_P
@ 2017-10-06  7:26 sergiodj+buildbot
  2017-10-25  5:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06  7:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT daf1c414a48baf090f005ce4b319b6881d5d6872 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: daf1c414a48baf090f005ce4b319b6881d5d6872

x86: Add NEED_DYNAMIC_RELOCATION_P

Add NEED_DYNAMIC_RELOCATION_P which returns TRUE if dynamic relocation
is needed.

	* elf32-i386.c (X86_PCREL_TYPE_P): New.
	(elf_i386_check_relocs): Use NEED_DYNAMIC_RELOCATION_P.
	* elf64-x86-64.c (IS_X86_64_PCREL_TYPE): Renamed to ...
	(X86_PCREL_TYPE_P): This.
	(elf_x86_64_check_relocs): Use NEED_DYNAMIC_RELOCATION_P.
	Replace IS_X86_64_PCREL_TYPE with X86_PCREL_TYPE_P.
	(elf_x86_64_relocate_section): Replace IS_X86_64_PCREL_TYPE with
	X86_PCREL_TYPE_P.
	* elfxx-x86.h (NEED_DYNAMIC_RELOCATION_P): New.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add RESOLVED_LOCALLY_P
@ 2017-10-06  7:30 sergiodj+buildbot
  2017-10-26  1:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06  7:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2eba97c207399d8b541092a7b0a4428dc02f5cf1 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 2eba97c207399d8b541092a7b0a4428dc02f5cf1

Add RESOLVED_LOCALLY_P


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Add GENERATE_RELATIVE_RELOC_P
@ 2017-10-06  7:36 sergiodj+buildbot
  2017-10-26 22:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06  7:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f70656b2604eff12cea2e9bef27c1e00a3077f30 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: f70656b2604eff12cea2e9bef27c1e00a3077f30

x86: Add GENERATE_RELATIVE_RELOC_P

Add GENERATE_RELATIVE_RELOC_P which returns TRUE if dynamic relative
relocation should be generated.

	* elfxx-x86.h (GENERATE_RELATIVE_RELOC_P): New.
	* elf32-i386.c (elf_i386_relocate_section): Use it.
	* elf64-x86-64.c (elf_x86_64_relocate_section): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Add COPY_INPUT_RELOC_P
@ 2017-10-06  7:49 sergiodj+buildbot
  2017-10-29 11:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06  7:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e74399c47c76b8111651f41b52a05401852cf799 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: e74399c47c76b8111651f41b52a05401852cf799

x86: Add COPY_INPUT_RELOC_P

Add COPY_INPUT_RELOC_P which returns TRUE if input relocation should
be copied to output.

	* elfxx-x86.h (COPY_INPUT_RELOC_P): New.
	* elf32-i386.c (elf_i386_relocate_section): Use it.
	* elf64-x86-64.c (elf_x86_64_relocate_section): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] gdb: Fix decoding of ARM neon memory hint insns.
@ 2017-10-06  9:53 sergiodj+buildbot
  2017-11-01  1:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06  9:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f924de654ff8f719faf60b84948397809baaac6 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 2f924de654ff8f719faf60b84948397809baaac6

gdb: Fix decoding of ARM neon memory hint insns.

gdb/ChangeLog:

2017-10-05  Jose E. Marchesi  <jose.marchesi@oracle.com>

	PR build/22188
	* arm-tdep.c (arm_decode_misc_memhint_neon): Fix decoding of CPS
	and SETEND.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] [RFC] Replicate src dir in build dir
@ 2017-10-06 10:17 sergiodj+buildbot
  2017-11-01 23:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06 10:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f38307f593cb8189c82fb39e46e0cd899022e2fb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f38307f593cb8189c82fb39e46e0cd899022e2fb

[RFC] Replicate src dir in build dir

Nowadays, GDB build tree is almost flat, but source tree isn't.  We
have arch/ nat/ target/ common/ cli/ mi/ tui/ python/ guile/ directories.
We need to some rules in Makefile for source files in different source
directories, like,

 # Rules for compiling .c files in the various source subdirectories.
%.o: ${srcdir}/arch/%.c
	$(COMPILE) $<
	$(POSTCOMPILE)

%.o: ${srcdir}/nat/%.c
	$(COMPILE) $<
	$(POSTCOMPILE)

so we should take care of some special case that files' base name is the
same, like,

 # Specify an explicit rule for gdb/common/agent.c, to avoid a clash with the
 # object file generate by gdb/agent.c.
common-agent.o: $(srcdir)/common/agent.c
	$(COMPILE) $(srcdir)/common/agent.c
	$(POSTCOMPILE)

As we add more and more files in different directories, it becomes tricky
to name files, because we need take this into account.

This patch takes the first step toward "Replicate src dir in build dir",
that is, we create arch/ directory in buildtree, and put amd64.o there
as an example.  Dependency tracking is updated for files with directory
name.  Currently, when we build amd64.o,

  "-c -o amd64.o -MT amd64.o -MMD -MP -MF .deps/amd64.Tpo"

with this patch applied, it becomes,

  "-c -o arch/amd64.o -MT arch/amd64.o -MMD -MP -MF arch/.deps/amd64.o.Tpo"

"make clean" removes the object files, and "make distclean" removes .deps
additionally.  configure file create .deps directory in each of
CONFIG_SRC_SUBDIR, and pass it to Makefile.in, so that "make clean" and
"make distclean" can remove stuffs there.

If people agree with this change, I'll add more directories to
CONFIG_SRC_SUBDIR.

gdb:

2017-10-06  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (CONFIG_SRC_SUBDIR): New.
	(ALL_64_TARGET_OBS): Replace amd64.o with arch/amd64.o.
	(clean): Remove object files and dependency files.
	(distclean): Remove the directory.
	* configure.ac: Invoke AC_CONFIG_COMMANDS.
	* configure: Re-generated.
	* configure.tgt: Replace amd64.o with arch/amd64.o.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Share code updating gdb_target_obs
@ 2017-10-06 10:23 sergiodj+buildbot
  2017-11-02 19:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06 10:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d97987e219b80c670e37eb0e25e31b36fa295509 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: d97987e219b80c670e37eb0e25e31b36fa295509

Share code updating gdb_target_obs

Nowadays, there are much duplications in configure.tgt to update
gdb_target_obs, some cpu specific object files are added to gdb_target_obs
to some different target triplets of the same cpu.  The same problem
exists for os specific object files too.  It is fragile to update them,
and build with all targets enabled doesn't find the problem.

This patch splits the gdb_target_obs update to three steps, cpu steps, os
steps, and the rest.

I tested this patch by build gdb for each different target triplets
respectively,

aarch64-elf aarch64-rtems aarch64-freebsd aarch64-linux alpha-elf
alpha-linux alpha-netbsd alpha-openbsd arm-elf arm-wince-pe arm-linux
arm-netbsd arm-symbianelf avr cris-elf frv-elf h8300-elf i386-elf
i386-darwin i386-dicos i386-freebsd i386-netbsdelf i386-openbsd
i386-nto i386-solaris i386-linux i386-gnu i386-cygwin i386-mingw32
i386-go32 ia64-linux-gnu ia64-vms lm32-elf m32c-elf m32r-elf m32r-linux
m68hc11-elf m68k-elf m68k-linux m68k-netbsd m68k-openbsd m88k-openbsd
mep-elf microblaze-xilinx-elf microblaze-linux-gnu mips-elf moxie-elf
ms1-elf nios2-elf nios2-linux-gnu hppa-elf hppa-linux hppa-netbsd
hppa-openbsd powerpc-eabi powerpc-freebsd powerpc-netbsd powerpc-openbsd
powerpc-linux powerpc-lynx178 rl78-elf rx-elf s390-linux-gnu score-elf
sh-elf sh-linux sh-openbsd sh64-elf sh64-linux sh64-openbsd sparc64-linux
sparc-linux sparc-freebsd sparc64-freebsd sparc-netbsd sparc64-netbsd
sparc-openbsd sparc64-openbsd spu-elf tic6x-elf tic6x-uclinux v850-elf
vax-netbsd vax-openbsd x86_64-linux-gnu x86_64-darwin x86_64-dicos
x86_64-elf x86_64-freebsd x86_64-mingw32 x86_64-netbsd x86_64-openbsd
x86_64-rtems xstormy16-elf xtensa-elf xtensa-linux

gdb:

2017-10-06  Yao Qi  <yao.qi@linaro.org>

	* configure.tgt (i386_tobjs): New variable.
	(amd64_tobjs): New variable.
	Set $cpu_obs and $os_obs.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix more GDB build breakage on mingw32
@ 2017-10-06 11:06 sergiodj+buildbot
  2017-11-06  1:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06 11:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a1b85d282f408dfd18a27539874846197f7e4044 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a1b85d282f408dfd18a27539874846197f7e4044

Fix more GDB build breakage on mingw32

With F23's mingw gcc 5.3.0, I'm seeing:

 i686-w64-mingw32-g++ -x c++ -std=gnu++11 -g3 -O0   -I. -I../../src/gdb -I../../src/gdb/common -I../../src/gdb/config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I../../src/gdb/../include/opcode -I../../src/gdb/../opcodes/.. -I../../src/gdb/../readline/.. -I../../src/gdb/../zlib -I../bfd -I../../src/gdb/../bfd -I../../src/gdb/../include -I../libdecnumber -I../../src/gdb/../libdecnumber  -I../../src/gdb/gnulib/import -Ibuild-gnulib/import   -I/home/pedro/src/expat/install-win32//include   -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 -Wno-format -Werror -c -o windows-nat.o -MT windows-nat.o -MMD -MP -MF ./.deps/windows-nat.o.Tpo ../../src/gdb/windows-nat.c
 ../../src/gdb/windows-nat.c: In function 'void windows_create_inferior(target_ops*, const char*, const string&, char**, int)':
 ../../src/gdb/windows-nat.c:2476:7: error: 'replace' is not a member of 'std'
	std::replace (expanded_infcwd.begin (), expanded_infcwd.end (),
	^

gdb/Changelog:
2017-10-06  Pedro Alves  <palves@redhat.com>

	* windows-nat.c: Include <algorithm>.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Add "do/while(0); " to COPY_INPUT_RELOC_P/VERIFY_COPY_RELOC
@ 2017-10-06 12:54 sergiodj+buildbot
  2017-11-06 21:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06 12:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0d8f43169368abf354e596c7725dee1dd609cb8 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: e0d8f43169368abf354e596c7725dee1dd609cb8

Add "do/while(0);" to COPY_INPUT_RELOC_P/VERIFY_COPY_RELOC

Add "do/while(0);" to COPY_INPUT_RELOC_P/VERIFY_COPY_RELOC to avoid
potential dangling else problems.

	* elfxx-x86.h (COPY_INPUT_RELOC_P): Add "do/while(0);".
	(VERIFY_COPY_RELOC): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Move arm.o arm-get-next-pcs.o arm-linux.o to arch/
@ 2017-10-06 13:38 sergiodj+buildbot
  2017-11-08 17:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06 13:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71917808c3490b4d4df9c6e848e3c5d75f5278d2 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 71917808c3490b4d4df9c6e848e3c5d75f5278d2

Move arm.o arm-get-next-pcs.o arm-linux.o to arch/

It is tested by building GDB for some targets, arm-elf, arm-netbsd,
arm-linux, and aarch64-linux.

gdb:

2017-10-06  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (ALL_TARGET_OBS): Replace arm.o, arm-get-next-pcs.o,
	and arm-linux.o with arch/arm.o, arch/arm-get-next-pcs.o and
	arch/arm-linux.o respectively.
	* configure.tgt: Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Account for padding in FreeBSD/mipsn32 NT_PRSTATUS notes.
@ 2017-10-06 21:43 sergiodj+buildbot
  2017-11-10  9:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06 21:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 544c67cda1686c1b204cb96c0d7885b08d37b8d6 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 544c67cda1686c1b204cb96c0d7885b08d37b8d6

Account for padding in FreeBSD/mipsn32 NT_PRSTATUS notes.

Add a new ELF backend method to grok FreeBSD NT_PRSTATUS core dump
notes.  Define a method for MIPS N32 to override the default
elfcore_grok_freebsd_prstatus that accounts for additional padding
between pr_pid and pr_reg that is not present in other 32-bit FreeBSD
platforms.

	* elf-bfd.h (struct elf_backend_data): Add
	`elf_backend_grok_freebsd_prstatus'.
	* elf.c (elfcore_grok_freebsd_note): Call
	`elf_backend_grok_freebsd_prstatus' to handle NT_PRSTATUS if
	present.
	* elfn32-mips.c (elf_n32_mips_grok_freebsd_prstatus): New
	function.
	(elf_backend_grok_freebsd_prstatus): Define.
	* elfxx-target.h (elf_backend_grok_freebsd_prstatus): Define.
	(elfNN_bed): Initialize `elf_backend_grok_freebsd_prstatus'.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Skip gdb.mi/mi-threads-interrupt.exp if nointerrupts.
@ 2017-10-06 22:49 sergiodj+buildbot
  2017-11-11  5:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-06 22:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b3b7c423883ad8d8b81f166ad2d2d4b637086bc0 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: b3b7c423883ad8d8b81f166ad2d2d4b637086bc0

Skip gdb.mi/mi-threads-interrupt.exp if nointerrupts.

2017-10-06  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.mi/mi-threads-interrupt.exp: Skip test if nointerrupts.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Update UNDEFINED_WEAK_RESOLVED_TO_ZERO comments
@ 2017-10-07  0:08 sergiodj+buildbot
  2017-11-12 23:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-07  0:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99180bccaf09413c9ddb28e51fa30f1ca4966583 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 99180bccaf09413c9ddb28e51fa30f1ca4966583

x86: Update UNDEFINED_WEAK_RESOLVED_TO_ZERO comments

	* elfxx-x86.h (UNDEFINED_WEAK_RESOLVED_TO_ZERO): Update
	comments.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] x86: Use zero_undefweak in elf_x86_link_hash_entry
@ 2017-10-07  1:04 sergiodj+buildbot
  2017-11-12  2:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-07  1:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98b273dc13b1e45db8c66821efc9e514884f3c25 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 98b273dc13b1e45db8c66821efc9e514884f3c25

x86: Use zero_undefweak in elf_x86_link_hash_entry

Replace has_got_reloc and has_non_got_reloc in elf_x86_link_hash_entry
with zero_undefweak:

Bit 0: Symbol has no GOT nor PLT relocations.
Bit 1: Symbol has non-GOT/non-PLT relocations in text sections.

zero_undefweak is initialized to 1 and undefined weak symbol should be
resolved to 0 if zero_undefweak > 0.

	* elf32-i386.c (elf_i386_check_relocs): Replace has_got_reloc
	and has_non_got_reloc with zero_undefweak.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Likewise.
	* elfxx-x86.c (_bfd_x86_elf_link_hash_newfunc): Initialize
	zero_undefweak to 1.
	(_bfd_x86_elf_copy_indirect_symbol): Replace has_got_reloc and
	has_non_got_reloc with zero_undefweak.
	* elfxx-x86.h (UNDEFINED_WEAK_RESOLVED_TO_ZERO): Replace
	has_got_reloc and has_non_got_reloc with zero_undefweak.
	(elf_x86_link_hash_entry): Likewise.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] PR22212, memory leak in nm
@ 2017-10-09  5:11 sergiodj+buildbot
  2017-11-19  7:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-09  5:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b55ec8b676ed05d93ee49d6c79ae0403616c4fb0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: b55ec8b676ed05d93ee49d6c79ae0403616c4fb0

PR22212, memory leak in nm

	PR 22212
	* dwarf2.c (_bfd_dwarf2_cleanup_debug_info): Free
	funcinfo_hash_table and varinfo_hash_table.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Fix gdb.base/print-file-var-main.c value check logic
@ 2017-10-09 12:16 sergiodj+buildbot
  2017-11-24  8:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-09 12:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c9e4427a745e5e26fba320ecc62e4285b613e4f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5c9e4427a745e5e26fba320ecc62e4285b613e4f

Fix gdb.base/print-file-var-main.c value check logic

Fix a typo introduced in commit c56e7c4390ed ("Make ctxobj.exp and
print-file-var.exp work on all platforms.").

This doesn't really affect the outcome of the testcase.  I only
noticed the typo because I stepped through the program manually.

To avoid such problems if the test is extended, this moves the STOP
marker until after the program self-validates the values.  With the
typo in place, this alone would have resulted in a test FAIL.  I.e.,
it'd have caught the typo.

gdb/testsuite/ChangeLog:
2017-10-09  Pedro Alves  <palves@redhat.com>

	* gdb.base/print-file-var-main.c: Fix get_version_2 value check
	logic.  Move STOP marker after the value checks.
	* gdb.base/print-file-var.exp (continue to STOP marker): Tighten
	regexp.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] S/390: Sync with latest POP - 3 new instructions
@ 2017-10-09 17:56 sergiodj+buildbot
  2017-11-29 10:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-09 17:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8e464506d2131fc931c4f81a22cc7125b7adf434 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 8e464506d2131fc931c4f81a22cc7125b7adf434

S/390: Sync with latest POP - 3 new instructions

prno, tpei, and irbm are missing in the optable.

gas/ChangeLog:

2017-10-09  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* testsuite/gas/s390/zarch-arch12.d (prno, tpei, irbm): New
	instructions added.
	* testsuite/gas/s390/zarch-arch12.s: Likewise.
	* testsuite/gas/s390/zarch-z13.d: Rename ppno to prno.

opcodes/ChangeLog:

2017-10-09  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-opc.txt (prno, tpei, irbm): New instructions added.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
* [binutils-gdb] Don't try building gdb against guile-2.2
@ 2017-10-09 18:14 sergiodj+buildbot
  2017-12-02  3:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1995+ messages in thread
From: sergiodj+buildbot @ 2017-10-09 18:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e66f7538112d2f5fb1af17dbde33ba37a7171be ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 6e66f7538112d2f5fb1af17dbde33ba37a7171be

Don't try building gdb against guile-2.2

GDB currently doesn't build with Guile 2.2 (see PR 21104).  If one has
both Guile 2.2 and 2.0 installed, GDB will pick up Guile 2.2 first and
fail building.  Until somebody does the work of adapting the GDB code to
Guile 2.2, we should not try using it.  This patch therefore removes it
from configure.

gdb/ChangeLog:

	* configure.ac (try_guile_versions): Remove guile-2.2.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1995+ messages in thread
end of thread, other threads:[~2017-12-02  3:15 UTC | newest]

Thread overview: 1995+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-06-10 14:24 [binutils-gdb] Implement vFile:setfs in gdbserver sergiodj+buildbot
2015-06-10 14:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2015-06-10 14:29 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-06-10 14:31 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-06-10 23:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-06-11  2:20 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2015-06-11  3:00 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2015-06-11  3:02 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-06-11  3:28 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-06-11 10:25 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-06-11 12:14 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2015-06-11 12:40 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2015-06-11 19:57 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-06-12 19:04 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2016-01-02 19:11 [binutils-gdb] sim: cris: use standard output helpers sergiodj+buildbot
2016-01-02 20:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-03  5:29 [binutils-gdb] sim: convert to bfd_endian sergiodj+buildbot
2016-01-03  7:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-03  9:17 [binutils-gdb] sim: nrun: use lbasename sergiodj+buildbot
2016-01-03 10:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-03  9:29 [binutils-gdb] sim: use libiberty countargv in more places sergiodj+buildbot
2016-01-03 12:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-04  1:04 [binutils-gdb] sim: TODO: move to wiki sergiodj+buildbot
2016-01-04  2:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-04  3:17 [binutils-gdb] sim: parse_args: display getopt error ourselves sergiodj+buildbot
2016-01-04  4:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 20:31 [binutils-gdb] sim: msp430: switch to common disassembler tracing sergiodj+buildbot
2016-01-06  0:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 20:37 [binutils-gdb] Fix the execution of the MSP430 simulator testsuite sergiodj+buildbot
2016-01-05 20:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 20:39 [binutils-gdb] sim: bfin: add support disasm tracing sergiodj+buildbot
2016-01-06  2:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 20:40 [binutils-gdb] sim: trace: add support for disassembling sergiodj+buildbot
2016-01-05 23:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 21:02 [binutils-gdb] sim: aarch64: switch to common disassembler tracing sergiodj+buildbot
2016-01-06  3:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 21:27 [binutils-gdb] sim: msp430: drop duplicate sim_load_file call sergiodj+buildbot
2016-01-06  5:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 21:38 [binutils-gdb] Add myself as the maintainer for the AArch64 sergiodj+buildbot
2016-01-05 22:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 22:13 [binutils-gdb] gdb: score: drop sim file check sergiodj+buildbot
2016-01-06  6:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 22:21 [binutils-gdb] libiberty: fix warnings about left shifting a negative value sergiodj+buildbot
2016-01-06  8:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 22:29 [binutils-gdb] libiberty: Tweak the documentation of libiberty's xcrc32 function sergiodj+buildbot
2016-01-06  9:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 23:03 [binutils-gdb] libiberty: {count, dup, write}argv: constify argv input slightly sergiodj+buildbot
2016-01-06 12:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-05 23:23 [binutils-gdb] libiberty: dupargv: rewrite to use xstrdup sergiodj+buildbot
2016-01-06 10:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-06  4:40 [binutils-gdb] gdb: change version stamp to git sergiodj+buildbot
2016-01-06 13:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-06  5:52 [binutils-gdb] Change copyright owner to FSF in sim/testsuite/sim/mips/hilo-hazard-4.s sergiodj+buildbot
2016-01-06 14:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-06 11:46 [binutils-gdb] Fix gdb.python/py-infthread.exp test message typo sergiodj+buildbot
2016-01-06 16:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-06 14:28 [binutils-gdb] bfd/arc: Add R_ prefix to all relocation names sergiodj+buildbot
2016-01-06 17:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-06 15:10 [binutils-gdb] [ARM/AArch64] Fix -Werror=unused-const-variable warnings in GDBserver sergiodj+buildbot
2016-01-06 18:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-06 15:34 [binutils-gdb] Make {arm,thumb}_get_next_pcs_raw static sergiodj+buildbot
2016-01-06 20:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-06 18:52 [binutils-gdb] MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes sergiodj+buildbot
2016-01-06 21:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-07  2:58 [binutils-gdb] sim: sim_{create_inferior, open, parse_args}: constify argv/env slightly sergiodj+buildbot
2016-01-07  4:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-07  3:07 [binutils-gdb] sim: config: drop use of __DATE__/__TIME__ sergiodj+buildbot
2016-01-07  5:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-07 19:37 [binutils-gdb] MIPS: Complete `status' to `err' renaming in `mips_breakpoint_from_pc' sergiodj+buildbot
2016-01-07 20:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-08  9:58 [binutils-gdb] [ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE sergiodj+buildbot
2016-01-08 11:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-08 10:52 [binutils-gdb] m68k: fix constraints of move.[bw] for ISA_B/C sergiodj+buildbot
2016-01-08 12:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-08 11:16 [binutils-gdb] Check input interrupt first when reading packet sergiodj+buildbot
2016-01-08 13:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-08 11:25 [binutils-gdb] Change SIGINT handler for extension languages only when target terminal is ours sergiodj+buildbot
2016-01-08 15:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-08 15:34 [binutils-gdb] perf testsuite: python 3 fixes sergiodj+buildbot
2016-01-08 16:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-08 19:16 [binutils-gdb] Fix gdb.multi/base.exp testsuite regression sergiodj+buildbot
2016-01-08 20:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-09  9:01 [binutils-gdb] sim: drop common/cconfig.h in favor of a single config.h sergiodj+buildbot
2016-01-09 10:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-09  9:24 [binutils-gdb] sim: stop configuring common subdir sergiodj+buildbot
2016-01-09 11:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-10  8:17 [binutils-gdb] sim: drop --enable-sim-cflags option sergiodj+buildbot
2016-01-10  9:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-10  8:33 [binutils-gdb] sim: drop --enable-sim-{regparm,stdcall} options sergiodj+buildbot
2016-01-10 10:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-10  8:51 [binutils-gdb] sim: allow the inline configure option everywhere sergiodj+buildbot
2016-01-10 12:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-10  8:59 [binutils-gdb] sim: mips: drop SIM_AC_OPTION_SMP call sergiodj+buildbot
2016-01-10 13:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-10  9:12 [binutils-gdb] sim: drop targ-vals.def->nltvals.def indirection sergiodj+buildbot
2016-01-10 14:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-10 22:20 [binutils-gdb] sim: allow the assert configure option everywhere sergiodj+buildbot
2016-01-10 23:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-10 22:28 [binutils-gdb] sim: allow the environment configure option everywhere sergiodj+buildbot
2016-01-11  0:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-10 23:15 [binutils-gdb] sim: drop unused SIM_AC_OPTION_PACKAGES sergiodj+buildbot
2016-01-11  2:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-11  0:08 [binutils-gdb] sim: move many common settings from CPPFLAGS to config.h sergiodj+buildbot
2016-01-11  3:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-11  6:11 [binutils-gdb] sim: config: do not try to align settings sergiodj+buildbot
2016-01-11  7:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-11 11:18 [binutils-gdb] Import changes made to files shared with the FSF GCC project sergiodj+buildbot
2016-01-11 12:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-11 18:06 [binutils-gdb] Delete opcodes that have been removed from ISA 3.0 sergiodj+buildbot
2016-01-11 19:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-11 19:13 [binutils-gdb] gdb: split out warnings helpers sergiodj+buildbot
2016-01-11 20:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-11 21:16 [binutils-gdb] testsuite: Fix false FAILs on too long base directory sergiodj+buildbot
2016-01-11 22:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-11 21:25 [binutils-gdb] testsuite: Regression for foll-vfork.exp sergiodj+buildbot
2016-01-11 23:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-11 21:31 [binutils-gdb] testsuite: i386 regression for funcargs.exp sergiodj+buildbot
2016-01-12  1:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12  1:37 [binutils-gdb] Reapply: List inferiors/threads/pspaces in ascending order sergiodj+buildbot
2016-01-12  2:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12  6:46 [binutils-gdb] sim: mips: workaround 32-bit addr sign extensions sergiodj+buildbot
2016-01-12  8:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 12:01 [binutils-gdb] Hurd: Make gdb/reply_mig_hack.awk script compatible to "mawk" sergiodj+buildbot
2016-01-12 13:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 13:13 [binutils-gdb] Test gdb.base/random-signal.exp with "attach" sergiodj+buildbot
2016-01-12 14:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 15:09 [binutils-gdb] Remove trademark acknowledgements throughout sergiodj+buildbot
2016-01-12 17:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 15:22 [binutils-gdb] Change function signature passed to clone sergiodj+buildbot
2016-01-12 18:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 15:44 [binutils-gdb] gdbserver: fix various warnings sergiodj+buildbot
2016-01-12 20:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 15:45 [binutils-gdb] gdbserver: use the new gdb warning helpers sergiodj+buildbot
2016-01-12 21:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 16:34 [binutils-gdb] Fix invalid conversion from void * to gdb_byte * sergiodj+buildbot
2016-01-12 23:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 16:37 [binutils-gdb] Sync top-level Makefile.def with GCC sergiodj+buildbot
2016-01-13  0:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 16:41 [binutils-gdb] Add cantunwind when unwind info does not match start of section sergiodj+buildbot
2016-01-13  1:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 16:46 [binutils-gdb] [ARM] Support ARMv8.2 RAS extension sergiodj+buildbot
2016-01-13  3:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 16:49 [binutils-gdb] Sync top-level btool.m4 with GCC sergiodj+buildbot
2016-01-13  4:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-12 20:34 [binutils-gdb] Implement 'catch syscall' for gdbserver sergiodj+buildbot
2016-01-13  5:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-13 10:52 [binutils-gdb] Fix PR19388: Can't access $_siginfo in breakpoint (catch signal) condition sergiodj+buildbot
2016-01-13 12:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-13 11:35 [binutils-gdb] Add a new $_inferior convenience variable sergiodj+buildbot
2016-01-13 13:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-13 11:36 [binutils-gdb] Add Python InferiorThread.inferior attribute sergiodj+buildbot
2016-01-13 15:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-13 11:38 [binutils-gdb] Centralize thread ID printing sergiodj+buildbot
2016-01-13 16:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-13 11:39 [binutils-gdb] Per-inferior/Inferior-qualified thread IDs sergiodj+buildbot
2016-01-13 17:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-13 11:40 [binutils-gdb] Add Python InferiorThread.global_num attribute sergiodj+buildbot
2016-01-13 19:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-13 11:41 [binutils-gdb] Implement "info threads -gid" sergiodj+buildbot
2016-01-13 20:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-13 11:42 [binutils-gdb] Add $_gthread convenience variable sergiodj+buildbot
2016-01-13 21:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-13 16:19 [binutils-gdb] Read instruction with byte_order_for_code sergiodj+buildbot
2016-01-13 23:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-13 18:04 [binutils-gdb] MAINTAINERS: Add Andreas Arnez as s390 target maintainer sergiodj+buildbot
2016-01-14  0:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-14  9:39 [binutils-gdb] [ARM] Make thumb2_breakpoint static again sergiodj+buildbot
2016-01-14 11:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-14 11:03 [binutils-gdb] [AArch64] Fix missing architecture checks for ARMv8.2 system registers sergiodj+buildbot
2016-01-14 12:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-14 12:30 [binutils-gdb] Fix C++ build error by casting void * sergiodj+buildbot
2016-01-14 13:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-14 14:57 [binutils-gdb] [ARM] Remove field syscall_next_pc in struct gdbarch_tdep sergiodj+buildbot
2016-01-14 16:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-14 16:27 [binutils-gdb] Fix display of RL78 MOVW instructions that use the stack pointer sergiodj+buildbot
2016-01-14 17:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-15 21:59 [binutils-gdb] Fix "thread apply $conv_var" and misc other related problems sergiodj+buildbot
2016-01-15 23:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-15 22:25 [binutils-gdb] Star wildcard ranges (e.g., "info thread 2.*") sergiodj+buildbot
2016-01-16  0:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-15 22:55 [binutils-gdb] Fix phony_iconv wide character support sergiodj+buildbot
2016-01-16  1:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-17  3:05 [binutils-gdb] Regen configure sergiodj+buildbot
2016-01-17  4:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-17  5:43 [binutils-gdb] minor reformatting in sim/common/sim-fpu.c sergiodj+buildbot
2016-01-17  6:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-17  6:14 [binutils-gdb] Minor comment fixes in sim/common/sim-fpu.c sergiodj+buildbot
2016-01-17  8:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-17  6:17 [binutils-gdb] fix gdb version parsing in src-release.sh sergiodj+buildbot
2016-01-17  9:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-17  7:04 [binutils-gdb] GDB SIGSEGV opening a Fortran program compiled with ifort sergiodj+buildbot
2016-01-17 10:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 11:57 [binutils-gdb] Fix gdbserver build failure on targets without fork sergiodj+buildbot
2016-01-18 13:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 12:05 [binutils-gdb] Provide AC_PROG_LEX that copes with LEX=missing from top-level sergiodj+buildbot
2016-01-18 14:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 14:40 [binutils-gdb] [testsuite] @progbits -> %progbits sergiodj+buildbot
2016-01-18 15:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 15:11 [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_32bit sergiodj+buildbot
2016-01-18 17:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 15:19 [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_64bit sergiodj+buildbot
2016-01-18 18:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 16:03 [binutils-gdb] Fix PR threads/19422 - show which thread caused stop sergiodj+buildbot
2016-01-18 19:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 16:11 [binutils-gdb] Use a 32-bit value to hold the section number in the internal COFF symbol structure sergiodj+buildbot
2016-01-18 21:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 17:08 [binutils-gdb] testsuite: Remove unused global references in gdb_test sergiodj+buildbot
2016-01-18 22:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 21:22 [binutils-gdb] MIPS: Fix microMIPS instruction size determination sergiodj+buildbot
2016-01-19  0:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 22:01 [binutils-gdb] MIPS: Only build microMIPS specific simulator functions if microMIPS support is required sergiodj+buildbot
2016-01-19  1:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-18 22:31 [binutils-gdb] MIPS: Remove remnants of 48-bit microMIPS instruction support sergiodj+buildbot
2016-01-19  2:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 12:38 [binutils-gdb] Limit breakpoint re-set to the current program space sergiodj+buildbot
2016-01-19 15:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <bd0a71fa16f668341a9361c695bc3ca44d27b322@gdb-build>
2016-01-19 13:32 ` sergiodj+buildbot
2016-01-19 15:37 [binutils-gdb] Add PIC and TLS support to the ARC target sergiodj+buildbot
2016-01-19 16:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 15:50 [binutils-gdb] Fix detection of "r_fs" and "r_gs" on FreeBSD sergiodj+buildbot
2016-01-19 18:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 15:58 [binutils-gdb] testsuite: Make check-parallel return non-zero if a test failed sergiodj+buildbot
2016-01-19 19:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 16:07 [binutils-gdb] testsuite: Add --status to runtest invocation sergiodj+buildbot
2016-01-19 20:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 16:35 [binutils-gdb] testsuite: Factor out --status in DO_RUNTEST sergiodj+buildbot
2016-01-19 22:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 16:43 [binutils-gdb] Fix enum flag with Python 3 sergiodj+buildbot
2016-01-19 23:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 17:09 [binutils-gdb] Add support to readelf for reading FreeBSD ELF core notes sergiodj+buildbot
2016-01-20  0:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 17:18 [binutils-gdb] Add a pseudosection for the NT_FREEBSD_THRMISC note sergiodj+buildbot
2016-01-20  2:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 17:26 [binutils-gdb] Add support for extracting thread names from cores sergiodj+buildbot
2016-01-20  3:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 17:34 [binutils-gdb] Display per-thread information for threads in FreeBSD cores sergiodj+buildbot
2016-01-20  4:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 17:43 [binutils-gdb] Use LWP IDs with ptrace register requests on FreeBSD sergiodj+buildbot
2016-01-20  6:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 17:51 [binutils-gdb] Add support for LWP-based threads on FreeBSD sergiodj+buildbot
2016-01-20  7:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 18:00 [binutils-gdb] Dump register notes for each thread when generating a FreeBSD core sergiodj+buildbot
2016-01-20  8:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-19 23:43 [binutils-gdb] Use a separate variable for the size passed to sysctl sergiodj+buildbot
2016-01-20 10:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-20  4:14 [binutils-gdb] minor reformatting in printcmd.c::print_scalar_formatted sergiodj+buildbot
2016-01-20 11:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-20 13:05 [binutils-gdb] Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD sergiodj+buildbot
2016-01-20 14:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-20 14:43 [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR UAO sergiodj+buildbot
2016-01-20 15:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-20 17:40 [binutils-gdb] Fix missing IPA lib in tspeed.exp in some configurations sergiodj+buildbot
2016-01-20 18:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-20 18:53 [binutils-gdb] gnu_vector.exp: Respect `should_kfail' for PR 8549 sergiodj+buildbot
2016-01-20 20:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-20 19:03 [binutils-gdb] Fix sorting of enum values in FlagEnumerationPrinter sergiodj+buildbot
2016-01-20 21:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-21  8:17 [binutils-gdb] Detect the arm/thumb mode of code SIGRETURN or RT_SIGRETURN returns to sergiodj+buildbot
2016-01-21  9:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-21  9:40 [binutils-gdb] bfd/configure reorganisation sergiodj+buildbot
2016-01-21 10:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-21  9:57 [binutils-gdb] Convert macros in elf-linux-core.h to inline functions sergiodj+buildbot
2016-01-21 14:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-21 10:09 [binutils-gdb] Rename elf-linux-psinfo.h to elf-linux-core.h sergiodj+buildbot
2016-01-21 12:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-21 10:14 [binutils-gdb] [AArch64] Relax long branch veneer insertion for non STT_FUNC symbol sergiodj+buildbot
2016-01-21 15:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-21 10:33 [binutils-gdb] Fix regression introduced in "break *<EXPR>" by explicit location patches sergiodj+buildbot
2016-01-21 16:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-21 11:03 [binutils-gdb] Fix unexpected failures in the linker testsuite for ARM VxWorks targets sergiodj+buildbot
2016-01-21 18:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-21 11:45 [binutils-gdb] gdb: Respect CXXFLAGS when building with C++ compiler sergiodj+buildbot
2016-01-21 19:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-21 12:28 [binutils-gdb] gdb: Small cleanup to disasm.c:maybe_add_dis_line_entry sergiodj+buildbot
2016-01-21 21:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-21 14:04 [binutils-gdb] Fix compile time errors building ARC target on a 32-bit host sergiodj+buildbot
2016-01-21 23:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-22  0:30 [binutils-gdb] * lib/ada.exp (gdb_compile_ada): Fix typo sergiodj+buildbot
2016-01-22  1:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <f906b857015513af81f94db8e11b1e334c767def@gdb-build>
2016-01-22  0:32 ` sergiodj+buildbot
2016-01-22  1:15 [binutils-gdb] * breakpoint.c (init_breakpoint_sal): Add comment sergiodj+buildbot
2016-01-22  3:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-22  9:13 [binutils-gdb] [ARM] perror_with_name when failed to fetch/store registers sergiodj+buildbot
2016-01-22 10:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-22  9:39 [binutils-gdb] [testsuite] Unbuffer the output in gdb.base/multi-forks.c sergiodj+buildbot
2016-01-22 11:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <99e8eb11cfcdde8cba6755ed4613c3cb079dfaa4@gdb-build>
2016-01-22 15:28 ` sergiodj+buildbot
2016-01-22 17:04 [binutils-gdb] Reword the string description of native FreeBSD ptids sergiodj+buildbot
2016-01-22 18:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-22 20:50 [binutils-gdb] testsuite: Fix PR threads/19422 regression + Guile regression sergiodj+buildbot
2016-01-22 22:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-22 21:00 [binutils-gdb] testsuite: gdb.gdb/selftest.exp: Drop expected Thread number sergiodj+buildbot
2016-01-22 23:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <cc5fd9abe4980e48e2cc27b0225f3c6ba7c0756b@gdb-build>
2016-01-23 12:44 ` sergiodj+buildbot
     [not found] <dc29a1ce6a25233e608f90511e67af3c18e19a98@gdb-build>
2016-01-23 15:18 ` sergiodj+buildbot
2016-01-24  1:16 [binutils-gdb] MIPS/BFD: Correct register index calculation in BZ16_REG sergiodj+buildbot
2016-01-24  2:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-24  1:27 [binutils-gdb] MIPS/BFD: Simplify register index calculation in BZ16_REG_FIELD sergiodj+buildbot
2016-01-24  3:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-25  9:41 [binutils-gdb] Fix memory corruption on Mach-O systems by suppressing a memory tidy up sergiodj+buildbot
2016-01-25  9:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-25  9:54 [binutils-gdb] Add missing end-of-comment marker to previous delta. (Doh!) sergiodj+buildbot
2016-01-25 11:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-25 13:32 [binutils-gdb] Move foreach_with_prefix to lib/gdb.exp sergiodj+buildbot
2016-01-25 14:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <45f3854667c659ab053f51f96e1923f36e6e20ba@gdb-build>
2016-01-25 13:40 ` sergiodj+buildbot
2016-01-25 13:40 [binutils-gdb] Fix PR 19494: hang when killing unfollowed fork children sergiodj+buildbot
2016-01-25 16:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-25 13:48 [binutils-gdb] Fix PR 19461: strange "info thread" behavior in non-stop sergiodj+buildbot
2016-01-25 17:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-25 15:24 [binutils-gdb] [PATCH[ARM]Check mapping symbol while backward searching for IT block sergiodj+buildbot
2016-01-25 18:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-25 16:18 [binutils-gdb] ARC/BFD: Fix a build error from `index' shadowing a global declaration sergiodj+buildbot
2016-01-25 20:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-25 16:27 [binutils-gdb] Remove new_thread_notify and dead_thread_notify sergiodj+buildbot
2016-01-25 21:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <a579cd9aa8c57c8a54833f26452a1afef38e5d20@gdb-build>
2016-01-26  0:47 ` sergiodj+buildbot
2016-01-26 14:03 [binutils-gdb] [GDBserver] Check input interrupt after reading in a packet sergiodj+buildbot
2016-01-26 15:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-26 14:48 [binutils-gdb] Remove argument pc in get_next_pcs sergiodj+buildbot
2016-01-26 21:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-26 21:41 [binutils-gdb] Fix function comments sergiodj+buildbot
2016-01-26 23:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-27 11:38 [binutils-gdb] Add Keith Seitz as Linespec Maintainer sergiodj+buildbot
2016-01-27 13:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-28 15:47 [binutils-gdb] Import strchrnul from gnulib and use it sergiodj+buildbot
2016-01-28 19:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-28 21:00 [binutils-gdb] Sync libiberty with GCC sergiodj+buildbot
2016-01-28 22:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-29 20:45 [binutils-gdb] Fix two misleading indentation warnings sergiodj+buildbot
2016-01-29 22:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-01-31 20:38 [binutils-gdb] Fix /usr/bin/ld: final link failed: File truncated error on hppa sergiodj+buildbot
2016-01-31 22:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-01  3:01 [binutils-gdb] elf64-s390.c: Fix -Werror=misleading-indentation sergiodj+buildbot
2016-02-01  4:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-01  3:36 [binutils-gdb] Fix some comments in varobj.{c,h} sergiodj+buildbot
2016-02-01  6:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-01 13:53 [binutils-gdb] Add support for importing data from ILF images sergiodj+buildbot
2016-02-01 17:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-01 18:23 [binutils-gdb] gdb: New set/show max-value-size command sergiodj+buildbot
2016-02-01 19:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-01 19:35 [binutils-gdb] Test gdb.threads/forking-threads-plus-breakpoint.exp with displaced stepping off sergiodj+buildbot
2016-02-01 23:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-01 23:33 [binutils-gdb] gdb.base/skip.exp: Clean up multiple references to same test name sergiodj+buildbot
2016-02-02  1:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-01 23:59 [binutils-gdb] Don't add DT_NEEDED for unmatched symbol sergiodj+buildbot
2016-02-02  3:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-02 11:05 [binutils-gdb] Preparation for new siginfo on Linux sergiodj+buildbot
2016-02-02 14:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-02 11:38 [binutils-gdb] epiphany/disassembler: Improve alignment of output sergiodj+buildbot
2016-02-02 20:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-02 12:26 [binutils-gdb] Adaptation of siginfo fixup for the new bnd fields sergiodj+buildbot
2016-02-02 19:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-02 12:31 [binutils-gdb] Clear HAS_RELOC if there are no relocations sergiodj+buildbot
2016-02-03  0:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-02 13:44 [binutils-gdb] PowerPC64 ELFv2 entry code sergiodj+buildbot
2016-02-03  1:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-02 21:21 [binutils-gdb] Fix typos in bfd/ChangeLog and bfd/elf64-x86-64.c sergiodj+buildbot
2016-02-03  5:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-06  1:39 [binutils-gdb] sim: mips: fix prog_bfd usage sergiodj+buildbot
2016-02-06  3:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-07 14:56 [binutils-gdb] varobj: Cleanup dead code sergiodj+buildbot
2016-02-07 16:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-08 18:12 [binutils-gdb] remote.c: Cleanup unused variables sergiodj+buildbot
2016-02-08 19:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-08 19:12 [binutils-gdb] Fix in-tree, parallel running of Ada tests sergiodj+buildbot
2016-02-08 21:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-08 19:40 [binutils-gdb] Always organize test artifacts in a directory hierarchy sergiodj+buildbot
2016-02-08 23:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-09 10:10 [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow sergiodj+buildbot
2016-02-09 11:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-09 10:38 [binutils-gdb] Fix build breakage sergiodj+buildbot
2016-02-09 13:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-09 10:48 [binutils-gdb] Revert "Add a more helpful warning message to explain why some AArch64 relocations can overflow." sergiodj+buildbot
2016-02-09 15:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-09 10:57 [binutils-gdb] Revert "Fix build breakage" sergiodj+buildbot
2016-02-09 16:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-09 11:06 [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow sergiodj+buildbot
2016-02-09 18:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-09 12:41 [binutils-gdb] Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't sergiodj+buildbot
2016-02-09 22:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-09 14:16 [binutils-gdb] Modernize configure.ac's sergiodj+buildbot
2016-02-10  0:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-09 16:46 [binutils-gdb] Fix compile time warnings building the binutils with a gcc6 compiler sergiodj+buildbot
2016-02-10  2:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <8adce0342f5f50aba0154fc56ca59df45b219738@gdb-build>
2016-02-09 20:34 ` sergiodj+buildbot
2016-02-09 22:48 [binutils-gdb] Refactor string_to_event_location for legacy linespec support sergiodj+buildbot
2016-02-10  4:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-09 23:05 [binutils-gdb] Use string_to_event_location_basic in guile sergiodj+buildbot
2016-02-10  8:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-09 23:32 [binutils-gdb] Enable/update legacy linespecs in MI sergiodj+buildbot
2016-02-10  9:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-10  4:06 [binutils-gdb] Update NEWS post GDB 7.11 branch creation sergiodj+buildbot
2016-02-10 18:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-10 17:06 [binutils-gdb] Clear *VAL in regcache_raw_read_unsigned sergiodj+buildbot
2016-02-11 19:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <473b99e5721ad623cc5826e03a73e2cf6cef4eb5@gdb-build>
2016-02-11  9:53 ` sergiodj+buildbot
     [not found] <62e5fd57bcdfb58eadd08ec430c4dfd742027d8e@gdb-build>
2016-02-11 13:20 ` sergiodj+buildbot
2016-02-11 20:15 [binutils-gdb] Add missing quotes to gdb/testsuite/README sergiodj+buildbot
2016-02-12 15:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <9f5fed7852cae412443957862d759660cfcb3fd5@gdb-build>
2016-02-12  4:14 ` sergiodj+buildbot
     [not found] <7cae9051edc2e3b11b5c79c08edfb91ee7f4e2e4@gdb-build>
2016-02-12 17:31 ` sergiodj+buildbot
     [not found] <d21b5f15d92bc1902b9e57198f67550326c887d7@gdb-build>
2016-02-13  0:43 ` sergiodj+buildbot
     [not found] <020ecd38e74681cb14987baf1a4d3c3ee3be0006@gdb-build>
2016-02-13  2:23 ` sergiodj+buildbot
2016-02-14  8:44 [binutils-gdb] testsuite: Fix false Fortran regressions with recent gcc sergiodj+buildbot
2016-02-14 13:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-15 11:25 [binutils-gdb] Enhance GAS's .section directive so that it can take numeric values for the flags and type fields. (ELF only) sergiodj+buildbot
2016-02-15 14:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-15 17:01 [binutils-gdb] testsuite: Fix some tests that write outside of the standard output directory sergiodj+buildbot
2016-02-15 19:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-16  0:16 [binutils-gdb] Add parentheses to prevent truncated addresses sergiodj+buildbot
2016-02-16  4:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-16  0:37 [binutils-gdb] Fix BFD format matching for x86_64-w64-mingw32 -m32 LTO sergiodj+buildbot
2016-02-16  5:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-16 20:52 [binutils-gdb] Whitespace cleanup for skip testcase sergiodj+buildbot
2016-02-17  3:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-17 17:04 [binutils-gdb] Add missing cleanup in exec_file_locate_attach sergiodj+buildbot
2016-02-17 18:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-18 12:18 [binutils-gdb] Set breakpoint condition-evaluation in forking-threads-plus-breakpoint.exp sergiodj+buildbot
2016-02-18 14:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-18 21:14 [binutils-gdb] Add D support to gdb_default_target_compile sergiodj+buildbot
2016-02-19  0:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <f79a3bae8725dfe0e11b04ddfc6e6bc8f23e4e4e@gdb-build>
2016-02-18 21:29 ` sergiodj+buildbot
2016-02-19 16:10 [binutils-gdb] Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary sergiodj+buildbot
2016-02-19 19:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-21 20:46 [binutils-gdb] Remove search_parents parameter from d_lookup_symbol_imports sergiodj+buildbot
2016-02-21 21:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-21 21:15 [binutils-gdb] Also update recursive call to d_lookup_symbol_imports sergiodj+buildbot
2016-02-21 22:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-22 16:37 [binutils-gdb] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print' sergiodj+buildbot
2016-02-22 21:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-23 13:32 [binutils-gdb] Make linker assigned symbol dynamic only for shared object sergiodj+buildbot
2016-02-23 16:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-23 18:34 [binutils-gdb] arm-tdep.c: Remove unused "to" parameters sergiodj+buildbot
2016-02-23 20:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-23 21:37 [binutils-gdb] Extend "skip" command to support -file, -gfile, -function, -rfunction sergiodj+buildbot
2016-02-23 23:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-24  3:22 [binutils-gdb] Build unavailable-stack frames for tracepoint sergiodj+buildbot
2016-02-24  4:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-24 14:09 [binutils-gdb] [OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2 sergiodj+buildbot
2016-02-24 20:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-24 14:22 [binutils-gdb] [OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support sergiodj+buildbot
2016-02-24 23:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-24 17:45 [binutils-gdb] powerpc: Support z-point type in gdbserver sergiodj+buildbot
2016-02-25  3:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-24 18:24 [binutils-gdb] Move new skip features to proper section (post 7.11) sergiodj+buildbot
2016-02-25  5:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <338435ef105ff51e967571ad073830ec1eb5a4ab@gdb-build>
2016-02-25  9:03 ` sergiodj+buildbot
2016-02-25 12:24 [binutils-gdb] Add elf_x86_64_need_pic sergiodj+buildbot
2016-02-25 14:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-25 17:42 [binutils-gdb] avoid compiler warnings in remote-m32r-sdi.c sergiodj+buildbot
2016-02-26  3:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <7337a6f2297cdd91bb852b479b284e5796d62cc9@gdb-build>
2016-02-25 18:35 ` sergiodj+buildbot
2016-02-26 14:51 [binutils-gdb] Properly implement STT_COMMON sergiodj+buildbot
2016-02-26 18:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-26 20:20 [binutils-gdb] Add x86_64-*-rtems* target sergiodj+buildbot
2016-02-27  6:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-28 15:25 [binutils-gdb] Don't recursively look for a symbol in all imports of imported modules sergiodj+buildbot
2016-02-28 16:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-29 16:58 [binutils-gdb] Support more syscalls in linux-record: pipe2 epoll_create1 eventfd2 fallocate dup3 and inotify_init1 sergiodj+buildbot
2016-02-29 20:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-02-29 17:29 [binutils-gdb] aarch64-linux process record: more syscalls sergiodj+buildbot
2016-03-01 10:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-01 11:55 [binutils-gdb] S390: Fix internal error with stackless inferior sergiodj+buildbot
2016-03-01 14:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-01 12:05 [binutils-gdb] S390: Fix output path for s390-tdbregs test case sergiodj+buildbot
2016-03-01 16:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-01 15:41 [binutils-gdb] Fix output path for arm-disp-step.exp sergiodj+buildbot
2016-03-01 19:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-01 17:53 [binutils-gdb] Fix gdb.threads/watchpoint-fork*.c compilation sergiodj+buildbot
2016-03-01 22:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-01 18:47 [binutils-gdb] Fix gdb.trace/ftrace-lock.c compilation sergiodj+buildbot
2016-03-02  3:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-02  4:03 [binutils-gdb] Regenerate bfd files sergiodj+buildbot
2016-03-02  6:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-02 16:16 [binutils-gdb] testsuite: Remove unnecessary code in fortran vla-history test sergiodj+buildbot
2016-03-03  1:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-02 16:31 [binutils-gdb] [OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded sergiodj+buildbot
2016-03-03  3:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-02 17:06 [binutils-gdb] testsuite: Fix timeout issues during print of vla-arrays sergiodj+buildbot
2016-03-03  0:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-03  9:42 [binutils-gdb] Refactor gdb.base/disp-step-syscall.exp for general step over test sergiodj+buildbot
2016-03-03 12:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-03  9:51 [binutils-gdb] Step over syscalll insn with disp-step on and off sergiodj+buildbot
2016-03-03 14:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-03 10:00 [binutils-gdb] Step over fork/vfork syscall insn in gdbserver sergiodj+buildbot
2016-03-03 16:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-03 10:09 [binutils-gdb] Rename disp-step-syscall.exp to step-over-syscall.exp sergiodj+buildbot
2016-03-03 17:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-03 10:20 [binutils-gdb] Reformat gdb.base/step-over-syscall.exp sergiodj+buildbot
2016-03-03 19:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-03 15:34 [binutils-gdb] Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions sergiodj+buildbot
2016-03-04  1:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-03 19:03 [binutils-gdb] gdb.base/skip.exp: Use with_test_prefix sergiodj+buildbot
2016-03-04  2:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-03 21:03 [binutils-gdb] get_symbols() plugin API tweak to support --start-lib/--end-lib sergiodj+buildbot
2016-03-04  4:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-03 21:12 [binutils-gdb] Add new plugin hooks to support querying section alignment and size sergiodj+buildbot
2016-03-04 11:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-04 14:50 [binutils-gdb] Treat common symbol in executable as definition sergiodj+buildbot
2016-03-04 16:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-04 16:41 [binutils-gdb] Add missing ChangeLog entries for commit 82838 sergiodj+buildbot
2016-03-05 12:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-06  1:57 [binutils-gdb] Improve analysis of racy testcases sergiodj+buildbot
2016-03-06 22:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-07 15:51 [binutils-gdb] [AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced sergiodj+buildbot
2016-03-07 18:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-07 16:52 [binutils-gdb] Fix "set architecture mips:10000" crash sergiodj+buildbot
2016-03-07 20:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-07 17:40 [binutils-gdb] Allow zero length archive elements sergiodj+buildbot
2016-03-08 13:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09  3:19 [binutils-gdb] Assert that a floating type's length is at least as long as its format sergiodj+buildbot
2016-03-09  5:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09  3:39 [binutils-gdb] [CRIS] Don't internal error if forced big endian sergiodj+buildbot
2016-03-09  9:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09  4:23 [binutils-gdb] Fix floating conversion buffer overrun when host/target format matches sergiodj+buildbot
2016-03-09  7:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09  4:57 [binutils-gdb] Don't create dynamic sections when relocatable sergiodj+buildbot
2016-03-09 11:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09  6:37 [binutils-gdb] Allow zero length archive elements sergiodj+buildbot
2016-03-09 15:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 16:08 [binutils-gdb] [FR-V] Handle FR300 sergiodj+buildbot
2016-03-09 20:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 16:19 [binutils-gdb] Avoid spaces in osabi names sergiodj+buildbot
2016-03-09 22:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 16:30 [binutils-gdb] S390: Add use of unavailable-stack frame ID sergiodj+buildbot
2016-03-09 23:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 16:41 [binutils-gdb] S390: Recognize special jumps in prologue parser sergiodj+buildbot
2016-03-10  1:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 18:02 [binutils-gdb] gdb: Add ax_pseudo_register_collect for powerpc sergiodj+buildbot
2016-03-10  3:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 18:28 [binutils-gdb] gdb: Add gen_return_address for powerpc sergiodj+buildbot
2016-03-10  4:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 20:15 [binutils-gdb] Eliminate async_annotation_suffix sergiodj+buildbot
2016-03-10 21:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 20:27 [binutils-gdb] Update prompt_for_continue comments sergiodj+buildbot
2016-03-10 23:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 20:47 [binutils-gdb] Use struct buffer in gdb_readline_no_editing sergiodj+buildbot
2016-03-11  3:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 21:19 [binutils-gdb] Command line input handling TLC sergiodj+buildbot
2016-03-11  8:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-09 21:46 [binutils-gdb] gdb: fix doc string of target_can_use_hardware_watchpoint sergiodj+buildbot
2016-03-11  9:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-10 15:43 [binutils-gdb] Mark the i370 target as obsolete sergiodj+buildbot
2016-03-11 13:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-10 22:34 [binutils-gdb] Add $_as_string convenience function sergiodj+buildbot
2016-03-11 15:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-14 16:56 [binutils-gdb] gdb.base/default.exp: Add missing $_as_string to "show convenience" test sergiodj+buildbot
2016-03-14 18:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-14 20:28 [binutils-gdb] Regenerate bfd-in2.h sergiodj+buildbot
2016-03-15 11:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-16 16:29 [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions sergiodj+buildbot
2016-03-16 19:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-16 17:48 [binutils-gdb] xml-tdesc.c (tdesc_start_enum): Fix c++ build sergiodj+buildbot
2016-03-17 11:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-16 22:29 [binutils-gdb] PR remote/19496, interrupted syscall in forking-threads-plus-bkpt sergiodj+buildbot
2016-03-17 16:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-17  9:19 [binutils-gdb] linux-record: Fix bad fall-through for pipe/pipe2 sergiodj+buildbot
2016-03-17 22:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-18 15:45 [binutils-gdb] Make sparc_software_single_step static sergiodj+buildbot
2016-03-19  8:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-21 11:29 [binutils-gdb] ARM process record: median instructions sergiodj+buildbot
2016-03-21 16:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-29 10:50 [binutils-gdb] Tidy up AArch64 simulator code sergiodj+buildbot
2016-03-29 13:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-29 21:56 [binutils-gdb] gdbserver/s390: Switch on tracepoint support sergiodj+buildbot
2016-03-29 23:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-30 14:16 [binutils-gdb] Fix a seg-fault in the AVR linker sergiodj+buildbot
2016-03-30 15:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-31 11:40 [binutils-gdb] enable -Wwrite-strings for gas sergiodj+buildbot
2016-03-31 13:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-03-31 12:58 [binutils-gdb] python: Use console format for output of gdb.execute command sergiodj+buildbot
2016-03-31 16:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-05 18:35 [binutils-gdb] Improve gdb_remote_download, remove gdb_download sergiodj+buildbot
2016-04-06  5:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-05 19:25 [binutils-gdb] Make ftrace tests work with remote targets sergiodj+buildbot
2016-04-06  7:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-05 22:02 [binutils-gdb] arc/nps400: Add additional instructions sergiodj+buildbot
2016-04-06  9:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-06  1:00 [binutils-gdb] Fix IPA detection in ftrace-insn-reloc.exp sergiodj+buildbot
2016-04-06 10:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-06  7:08 [binutils-gdb] testsuite: Update py-mi-objfile to expect console format print sergiodj+buildbot
2016-04-06 12:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-06 21:04 [binutils-gdb] Fix gdb.threads/dlopen-libpthread.exp crash sergiodj+buildbot
2016-04-07  0:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-06 21:44 [binutils-gdb] Optimized-out pointer: New test for error handling sergiodj+buildbot
2016-04-07  1:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-07 16:30 [binutils-gdb] Make breakpoint handling in record-full idempotent sergiodj+buildbot
2016-04-07 19:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-07 17:21 [binutils-gdb] Fix gdb.reverse/finish-reverse-bkpt.exp sergiodj+buildbot
2016-04-07 22:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-07 17:52 [binutils-gdb] gas/arc: Handle multiple arc_opcode chains for same mnemonic sergiodj+buildbot
2016-04-08  0:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-07 18:15 [binutils-gdb] arc/nps400: Add new instructions sergiodj+buildbot
2016-04-08  2:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-07 19:12 [binutils-gdb] Fix gdb.compile/compile.exp shlib regression sergiodj+buildbot
2016-04-08  3:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-12 10:00 [binutils-gdb] Add support for .extCondCode, .extCoreRegister and .extAuxRegister sergiodj+buildbot
2016-04-13  0:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-12 20:57 [binutils-gdb] Use target_terminal_ours_for_output in warning/internal_error sergiodj+buildbot
2016-04-14 14:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-13  8:11 [binutils-gdb] Do target_terminal_ours in query & friends instead of in all callers sergiodj+buildbot
2016-04-14 17:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-16  2:42 [binutils-gdb] gdb/ada-exp.y: Remap yydefred sergiodj+buildbot
2016-04-17 12:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-19 17:34 [binutils-gdb] symmisc.c (dump_symtab_1, dump_symtab): Delete arg objfile sergiodj+buildbot
2016-04-20  2:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-20 22:27 [binutils-gdb] Build GDB as a C++ program by default sergiodj+buildbot
2016-04-21 16:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-21  0:21 [binutils-gdb] Don't check relocations in excluded sections sergiodj+buildbot
2016-04-21 19:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-21  0:25 [binutils-gdb] Remove x86 gc_sweep_hook sergiodj+buildbot
2016-04-21 23:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-21 13:06 [binutils-gdb] Fix AIX gdb build with C++ compiler sergiodj+buildbot
2016-04-22  9:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-21 16:36 [binutils-gdb] Switch gdb's TRY/CATCH to sjlj again sergiodj+buildbot
2016-04-22 15:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-04-29 15:45 [binutils-gdb] Pass GOT_RELOC to UNDEFINED_WEAK_RESOLVED_TO_ZERO sergiodj+buildbot
2016-04-29 18:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-03 11:27 [binutils-gdb] [AArch64] Also puts value in place for R_AARCH64_RELATIVE sergiodj+buildbot
2016-05-03 21:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-03 12:30 [binutils-gdb] Fix gdb/python/python.c use-after-free sergiodj+buildbot
2016-05-04  1:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-09 13:29 [binutils-gdb] [ARM/STM32L4XX] PR 20030: --fix-stm32l4xx-629360 fails to create vldm/vpop veneers for double-precision registers sergiodj+buildbot
2016-05-09 19:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-13 18:25 [binutils-gdb] Don't convert GOTPCREL relocation against large section sergiodj+buildbot
2016-05-13 20:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-25 17:39 [binutils-gdb] Reimplement .no87/.nommx/.nosse/.noavx directives sergiodj+buildbot
2016-05-26 20:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-26 10:15 [binutils-gdb] metag: add extern C to header sergiodj+buildbot
2016-05-27 10:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-26 11:56 [binutils-gdb] MIPS/BFD: Don't stop processing on `bfd_reloc_outofrange' sergiodj+buildbot
2016-05-27 12:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-27 12:58 [binutils-gdb] gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT sergiodj+buildbot
2016-05-27 18:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-27 13:49 [binutils-gdb] Fix typo introduced during the most recent synchronization update sergiodj+buildbot
2016-05-27 22:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-27 14:08 [binutils-gdb] Correct CpuMax in i386-opc.h sergiodj+buildbot
2016-05-28  0:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-27 15:15 [binutils-gdb] Replace CpuAMD64/CpuIntel64 with AMD64/Intel64 sergiodj+buildbot
2016-05-28  2:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-27 15:32 [binutils-gdb] Skip attach-many-short-lived-threads.exp on known-broken DejaGnu versions sergiodj+buildbot
2016-05-28  2:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-27 17:19 [binutils-gdb] Update x86 CPU_XXX_FLAGS handling sergiodj+buildbot
2016-05-28  4:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-27 21:56 [binutils-gdb] MIPS/BFD: Fix section symbol name fetching in relocation sergiodj+buildbot
2016-05-28  6:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-27 22:07 [binutils-gdb] MIPS/BFD: Include the addend in JALX's target alignment verification sergiodj+buildbot
2016-05-28  7:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-28  2:08 [binutils-gdb] Return void from linker callbacks sergiodj+buildbot
2016-05-28  8:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-28 10:13 [binutils-gdb] MIPS/BFD: Enable local R_MIPS_26 overflow detection sergiodj+buildbot
2016-05-28 11:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-28 10:23 [binutils-gdb] MIPS/BFD: Correctly handle `bfd_reloc_outofrange' with branches sergiodj+buildbot
2016-05-28 12:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-28 13:19 [binutils-gdb] Add dependencies to configure rule sergiodj+buildbot
2016-05-28 14:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-29 15:10 [binutils-gdb] Add .noavx512XX directives to x86 assembler sergiodj+buildbot
2016-05-29 16:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-29 16:52 [binutils-gdb] NEWS: Remove empty line sergiodj+buildbot
2016-05-29 17:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-29 18:59 [binutils-gdb] NEWS: QCatchSyscalls: simplify sergiodj+buildbot
2016-05-29 19:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-30 12:29 [binutils-gdb] Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum sergiodj+buildbot
2016-05-30 13:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-30 12:38 [binutils-gdb] PR 15231: import bare DW_TAG_lexical_block sergiodj+buildbot
2016-05-30 14:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-30 17:04 [binutils-gdb] Add counter-cases for trace-condition.exp tests sergiodj+buildbot
2016-05-30 17:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-30 17:13 [binutils-gdb] Move trace conditions tests from ftrace.exp to trace-condition.exp sergiodj+buildbot
2016-05-30 18:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-30 17:22 [binutils-gdb] Add emit_less_unsigned test in trace-condition.exp sergiodj+buildbot
2016-05-30 19:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-30 17:30 [binutils-gdb] Add variable length tests for emit_ref in trace-condition.exp sergiodj+buildbot
2016-05-30 21:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-30 17:39 [binutils-gdb] Add tests for 64bit values in trace-condition.exp sergiodj+buildbot
2016-05-30 21:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-31 11:20 [binutils-gdb] Don't needlessly clear xmemdup allocated memory sergiodj+buildbot
2016-05-31 12:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-05-31 19:07 [binutils-gdb] [PR gdb/19893] Fix handling of synthetic C++ references sergiodj+buildbot
2016-05-31 20:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-01  3:22 [binutils-gdb] sh: make constant unsigned to avoid narrowing sergiodj+buildbot
2016-06-01  4:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-01  8:46 [binutils-gdb] Wake up interruptible_select in remote_fileio ctrl-c handler sergiodj+buildbot
2016-06-01  9:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-01  9:27 [binutils-gdb] infcmd, btrace: fix crash in 'finish' for tailcall-only frames sergiodj+buildbot
2016-06-01 10:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-01 10:56 [binutils-gdb] Add xmalloc_failed() function to common-utils.c in to avoid the need to link in libiberty's xmalloc code sergiodj+buildbot
2016-06-01 11:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-01 15:39 [binutils-gdb] Add support for some variants of the ARC nps400 rflt instruction sergiodj+buildbot
2016-06-01 16:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-01 15:48 [binutils-gdb] gdb/remote-fileio.c: Eliminate custom SIGINT signal handler sergiodj+buildbot
2016-06-01 17:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-01 16:03 [binutils-gdb] Add new Serbian translation for the bfd library sergiodj+buildbot
2016-06-01 18:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-02  1:33 [binutils-gdb] add more extern C sergiodj+buildbot
2016-06-02  2:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-02  3:32 [binutils-gdb] Revert PR16467 change sergiodj+buildbot
2016-06-02  4:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-02 13:17 [binutils-gdb] Add support for 48 and 64 bit ARC instructions sergiodj+buildbot
2016-06-02 13:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-02 14:30 [binutils-gdb] Replace data32 with data16 in comments sergiodj+buildbot
2016-06-02 15:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-02 15:31 [binutils-gdb] Allow ARC Linux targets that do not use uclibc sergiodj+buildbot
2016-06-02 16:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-02 16:28 [binutils-gdb] Add "arm_any" architecture type to allow -m option to various binutils to match any ARM architecture sergiodj+buildbot
2016-06-02 18:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-02 19:39 [binutils-gdb] Fix PR python/18984 sergiodj+buildbot
2016-06-02 20:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-03 11:47 [binutils-gdb] Fix C++ build for Cygwin sergiodj+buildbot
2016-06-03 13:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-03 23:15 [binutils-gdb] Handle indirect branches for AMD64 and Intel64 sergiodj+buildbot
2016-06-04  0:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-03 23:50 [binutils-gdb] Re-add support for lbarx, lharx, stbcx. and sthcx. insns back to the E6500 cpu sergiodj+buildbot
2016-06-04  1:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-04 20:35 [binutils-gdb] Add z8k ld testsuite and fix range check in coff-z8k.c sergiodj+buildbot
2016-06-04 21:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-06 18:25 [binutils-gdb] Support x86-64 TLS code sequences without PLT sergiodj+buildbot
2016-06-06 20:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-06 21:21 [binutils-gdb] Add method/format information to =record-started sergiodj+buildbot
2016-06-06 22:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-07  9:09 [binutils-gdb] [ARM] Add command line option for RAS extension sergiodj+buildbot
2016-06-07 11:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-07 11:49 [binutils-gdb] Frame static link: Handle null pointer sergiodj+buildbot
2016-06-07 13:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-07 13:02 [binutils-gdb] PowerPC VLE sergiodj+buildbot
2016-06-07 16:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-13 14:52 [binutils-gdb] [ARC] Generate DT_RELACOUNT sergiodj+buildbot
2016-06-13 17:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-21 15:18 [binutils-gdb] Push thread->control.command_interp to the struct thread_fsm sergiodj+buildbot
2016-06-23  7:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-21 16:33 [binutils-gdb] Make main_ui be heap allocated sergiodj+buildbot
2016-06-23 11:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-21 19:51 [binutils-gdb] [DOC] Document support for running interpreters on separate UIs sergiodj+buildbot
2016-06-23 21:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-22 11:03 [binutils-gdb] Send deleted watchpoint-scope output to all UIs sergiodj+buildbot
2016-06-24  2:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-23  9:16 [binutils-gdb] [ARC] Misc minor edits/fixes sergiodj+buildbot
2016-06-25  5:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-24 18:39 [binutils-gdb] Add elfcore_grok_freebsd_note to parse FreeBSD ELF core notes sergiodj+buildbot
2016-06-26  3:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-25 16:01 [binutils-gdb] xtensa: prototype xtensa_make_property_section in elf/xtensa.h sergiodj+buildbot
2016-06-27  6:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-28  0:55 [binutils-gdb] MIPS16: Add R_MIPS16_PC16_S1 branch relocation support sergiodj+buildbot
2016-06-28  2:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-28 11:18 [binutils-gdb] Don't convert R_SPARC_32 to R_SPARC_RELATIVE if class is ELFCLASS64 sergiodj+buildbot
2016-06-28 13:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-28 12:03 [binutils-gdb] Probe catch syscall support sergiodj+buildbot
2016-06-28 15:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-28 13:01 [binutils-gdb] Remove parameter sysret from linux_target_ops.get_syscall_trapinfo sergiodj+buildbot
2016-06-28 18:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-28 17:17 [binutils-gdb] [AArch64] Use int64_t for address offset sergiodj+buildbot
2016-06-29  6:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-28 18:34 [binutils-gdb] [TILEPro] Don't build gdb sergiodj+buildbot
2016-06-29 10:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-29 10:35 [binutils-gdb] Preserve all mapping symbols in ARM and AArch64 object files sergiodj+buildbot
2016-06-29 11:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-29 11:32 [binutils-gdb] Use strtok_r instead of strsep in rust_get_disr_info sergiodj+buildbot
2016-06-29 13:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-29 12:11 [binutils-gdb] sparc: make SPARC_OPCODE_ARCH_MAX part of its enum sergiodj+buildbot
2016-06-29 14:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-29 14:20 [binutils-gdb] Set unknown_syscall differently on arm linux sergiodj+buildbot
2016-06-29 16:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-29 14:59 [binutils-gdb] Initialize strtok_r's saveptr to NULL sergiodj+buildbot
2016-06-29 17:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-29 16:36 [binutils-gdb] PR gdb/17210 - fix possible memory leak in read_memory_robust sergiodj+buildbot
2016-06-29 18:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-29 16:58 [binutils-gdb] Fix PR python/20129 - use of non-existing variable sergiodj+buildbot
2016-06-29 20:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-29 18:30 [binutils-gdb] Add copyright header in gdb.base/return.c sergiodj+buildbot
2016-06-29 21:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-30  8:28 [binutils-gdb] Add support for simulating big-endian AArch64 binaries sergiodj+buildbot
2016-06-30 10:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-30 10:07 [binutils-gdb] [ARM][GAS] ARMv8.2 should enable ARMv8.1 NEON instructions sergiodj+buildbot
2016-06-30 11:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-30 11:28 [binutils-gdb] Make testing gdb with FORCE_SEPARATE_MI_TTY=1 actually work sergiodj+buildbot
2016-06-30 12:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-06-30 11:43 [binutils-gdb] Fix gdbserver/MI testing regression sergiodj+buildbot
2016-06-30 15:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01  7:09 [binutils-gdb] x86/Intel: fix operand checking for MOVSD sergiodj+buildbot
2016-07-01  8:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01  7:49 [binutils-gdb] x86: remove stray instruction attributes sergiodj+buildbot
2016-07-01  9:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01  8:42 [binutils-gdb] x86: allow suffix-less movzw and 64-bit movzb sergiodj+buildbot
2016-07-01 10:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 10:53 [binutils-gdb] Factor out "Detaching from program" message printing sergiodj+buildbot
2016-07-01 12:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 11:56 [binutils-gdb] Forget watchpoint locations when inferior exits or is killed/detached sergiodj+buildbot
2016-07-01 13:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 12:41 [binutils-gdb] Fix failure to detach if process exits while detaching on Linux sergiodj+buildbot
2016-07-01 14:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 12:59 [binutils-gdb] Extend JIT-reader test and fix GDB problems that exposes sergiodj+buildbot
2016-07-01 16:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 14:59 [binutils-gdb] Consolidate x86 debug register code for BSD native targets sergiodj+buildbot
2016-07-01 17:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 15:50 [binutils-gdb] Set debug registers on all threads belonging to the current inferior sergiodj+buildbot
2016-07-01 18:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 16:41 [binutils-gdb] Fix Thumb-2 BL detection sergiodj+buildbot
2016-07-01 20:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 17:17 [binutils-gdb] Honor detach-on-fork on FreeBSD sergiodj+buildbot
2016-07-01 21:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 18:19 [binutils-gdb] Move fbsd_resume and related functions below fork following helper code sergiodj+buildbot
2016-07-01 22:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 18:48 [binutils-gdb] Fake VFORK_DONE events when following only the parent after a vfork sergiodj+buildbot
2016-07-02  0:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 19:44 [binutils-gdb] [AArch64] Fix +nofp16 handling sergiodj+buildbot
2016-07-02  1:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-01 19:49 [binutils-gdb] Optimize memory_xfer_partial for remote sergiodj+buildbot
2016-07-02  2:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-05  9:02 [binutils-gdb] babeltrace compilation regression sergiodj+buildbot
2016-07-05 10:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-05 10:56 [binutils-gdb] [ARM] Change noread to purecode sergiodj+buildbot
2016-07-05 12:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-05 11:42 [binutils-gdb] [ARM] Purecode compatible long branch veneer for M-profile targets with MOVW sergiodj+buildbot
2016-07-05 13:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-05 14:06 [binutils-gdb] Fix fail in gdb.mi/mi-reverse.exp sergiodj+buildbot
2016-07-05 15:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-06  5:38 [binutils-gdb] Allow subscripting raw pointers sergiodj+buildbot
2016-07-06  6:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-06  7:38 [binutils-gdb] [ARM] Fix endless recursion on calculating CPRC candidate sergiodj+buildbot
2016-07-06  8:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-06 13:14 [binutils-gdb] Use 'ptid_t' instead of 'ptid' for fbsd_next_vfork_done's return type sergiodj+buildbot
2016-07-06 14:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-06 13:45 [binutils-gdb] Remove check for negative size sergiodj+buildbot
2016-07-06 15:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-06 14:25 [binutils-gdb] Set uses_fp for frames with a valid FP register explicitly sergiodj+buildbot
2016-07-06 17:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-06 15:28 [binutils-gdb] Use unsigned integer constant with left shifts sergiodj+buildbot
2016-07-06 18:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-06 15:43 [binutils-gdb] Remove extraneous parentheses sergiodj+buildbot
2016-07-19 16:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-07 15:52 [binutils-gdb] Fix of default lookup for "this" symbol sergiodj+buildbot
2016-07-20  2:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-13 21:51 [binutils-gdb] PR python/15620, PR python/18620 - breakpoint events in Python sergiodj+buildbot
2016-07-21 19:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-19 10:01 [binutils-gdb] Use do_self_tests in selftest.exp sergiodj+buildbot
2016-07-23 22:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-07-22 17:58 [binutils-gdb] Get "num" as unsigned in ctf sergiodj+buildbot
2016-07-27 11:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <7bd374a44d1db21b54a9a52ecde1d064cdaa8cd1@gdb-build>
2016-08-01  9:30 ` sergiodj+buildbot
2016-08-01 13:20 [binutils-gdb] Swap "single-process" and "multi-process" in process-dies-while-detaching.exp sergiodj+buildbot
2016-08-01 15:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-08-04 11:45 [binutils-gdb] Determine target description for native aarch64 sergiodj+buildbot
2016-08-04 15:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-08-05 22:57 [binutils-gdb] Remove unused cli_command_loop declaration sergiodj+buildbot
2016-08-07 20:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-08-09 20:38 [binutils-gdb] Correct the calculation of the use_counts of merged .got entries sergiodj+buildbot
2016-08-09 22:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-08-09 22:30 [binutils-gdb] Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions sergiodj+buildbot
2016-08-09 22:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-08-10  0:26 [binutils-gdb] Fix PR mi/20431 - Missing MI prompts after sync execution MI command (-exec-continue, etc.) errors sergiodj+buildbot
2016-08-10  1:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-08-10  1:19 [binutils-gdb] Fix PR gdb/20418 - Problems with synchronous commands and new-ui sergiodj+buildbot
2016-08-10  3:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-08-10 21:20 [binutils-gdb] Quiet ARI gettext checks sergiodj+buildbot
2016-08-10 22:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-08-11  0:35 [binutils-gdb] Support setting thread names (MS-Windows) sergiodj+buildbot
2016-08-11  0:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-08-20  9:29 [binutils-gdb] Fix missing files for ld when test suite not compiled in the source directory sergiodj+buildbot
2016-08-22 19:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-08-24 20:24 [binutils-gdb] Allow resetting an empty inferior-tty sergiodj+buildbot
2016-08-25  9:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-09-02  9:02 [binutils-gdb] Use target_continue{, _no_signal} instead of target_resume sergiodj+buildbot
2016-09-02  8:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-09-03 12:46 [binutils-gdb] Handle DW_OP_form_tls_address sergiodj+buildbot
2016-09-05 18:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-09-05 19:41 [binutils-gdb] Removed redundant line remote-utils.c sergiodj+buildbot
2016-09-05 20:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-09-06 23:37 [binutils-gdb] Add missing format for built-in floating-point types sergiodj+buildbot
2016-09-07 12:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-09-07  5:56 [binutils-gdb] Introduce make_cleanup_restore_current_ui sergiodj+buildbot
2016-09-09 18:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-09-15 21:47 [binutils-gdb] Modify POWER9 support to match final ISA 3.0 documentation sergiodj+buildbot
2016-09-15 21:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-09-19  6:16 [binutils-gdb] gdb: Fix std::{min, max}-related build breakage on 32-bit hosts sergiodj+buildbot
2016-09-20 13:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-09-19 16:45 [binutils-gdb] Consolidate target_mourn_inferior between GDB and gdbserver sergiodj+buildbot
2016-09-20 17:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-09-29 17:39 [binutils-gdb] Disallow 3-operand cmp[l][i] for ppc64 sergiodj+buildbot
2016-09-29 17:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-07  2:07 [binutils-gdb] Pass link_info to _bfd_merge_private_bfd_data sergiodj+buildbot
2016-10-08 20:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-07  7:22 [binutils-gdb] python: accept address and explicit locations in gdb.decode_line sergiodj+buildbot
2016-10-08 21:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-07 10:19 [binutils-gdb] [AArch64] PR target/20667, fix disassembler for the "special" optional SYS_Rt operand for "ic"/"tlbi" sergiodj+buildbot
2016-10-09  0:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-07 10:50 [binutils-gdb] Set regdir in tdesc-regs.exp or arm sergiodj+buildbot
2016-10-08 23:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-09  0:26 [binutils-gdb] ui-out.c: Remove unused parameter to push_level sergiodj+buildbot
2016-10-09  4:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-10  9:44 [binutils-gdb] Remove v850_dbtrap_breakpoint_from_pc sergiodj+buildbot
2016-10-10  9:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-10 10:37 [binutils-gdb] Rename 'arch' by 'gdbarch' in m32c_gdbarch_init sergiodj+buildbot
2016-10-10 11:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-10 11:41 [binutils-gdb] Share enum arm_breakpoint_kinds sergiodj+buildbot
2016-10-10 12:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-11  7:59 [binutils-gdb] Always descend into output section statements in lang_do_assignments sergiodj+buildbot
2016-10-11  7:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-11 10:42 [binutils-gdb] [AArch64] PR target/20666, fix wrong encoding of new introduced BFC pseudo sergiodj+buildbot
2016-10-11 10:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-11 15:00 [binutils-gdb] testsuite: Use standard_output_file sergiodj+buildbot
2016-10-11 15:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-11 17:27 [binutils-gdb] testsuite: Fix gdb.arch/powerpc-prologue.c compilation sergiodj+buildbot
2016-10-11 17:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-11 23:35 [binutils-gdb] BFD_FAKE_SECTION macro params sergiodj+buildbot
2016-10-11 23:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-12 11:51 [binutils-gdb] [AArch64] Track FP registers in prologue analyzer sergiodj+buildbot
2016-10-12 11:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-12 13:03 [binutils-gdb] arc: Add a gdbarch_tdep structure sergiodj+buildbot
2016-10-12 14:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-12 13:32 [binutils-gdb] arc: Add evaluation of long jump targets sergiodj+buildbot
2016-10-12 15:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-12 15:51 [binutils-gdb] Fixup gdb.python/py-value.exp for bare-metal aarch64-elf sergiodj+buildbot
2016-10-12 18:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-12 16:00 [binutils-gdb] arc: Add support for Newlib sergiodj+buildbot
2016-10-12 16:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-13  1:21 [binutils-gdb] Convert tid_range_parser and get_number_or_range to classes sergiodj+buildbot
2016-10-13  1:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-13  2:25 [binutils-gdb] Change selttest.c to use use std::vector sergiodj+buildbot
2016-10-13  2:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-13  2:59 [binutils-gdb] Turn wchar iterator into a class sergiodj+buildbot
2016-10-13  3:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-13  4:50 [binutils-gdb] Remove unnecessary null_cleanup sergiodj+buildbot
2016-10-13  5:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-13  5:24 [binutils-gdb] Use std::string in macho_symfile_read_all_oso sergiodj+buildbot
2016-10-13  6:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-13 14:54 [binutils-gdb] Skip testing structures with floating points sergiodj+buildbot
2016-10-13 14:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-13 15:27 [binutils-gdb] Share proc get_var_address sergiodj+buildbot
2016-10-13 16:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-13 17:38 [binutils-gdb] ARI: Remove true/false checks sergiodj+buildbot
2016-10-13 17:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-14  7:30 [binutils-gdb] Include strings.h where available sergiodj+buildbot
2016-10-14 17:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-14 13:25 [binutils-gdb] Fix set sysroot command on AIX sergiodj+buildbot
2016-10-15  6:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-14 16:29 [binutils-gdb] Move OVERRIDE/FINAL from gcc/coretypes.h to include/ansidecl.h sergiodj+buildbot
2016-10-15 10:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-17 13:56 [binutils-gdb] Removed pseudo invalid instructions opcodes sergiodj+buildbot
2016-10-17 19:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-17 16:34 [binutils-gdb] gdb: Fix phony iconv build sergiodj+buildbot
2016-10-17 22:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-17 21:05 [binutils-gdb] Fix -trace-save crash when argument is missing sergiodj+buildbot
2016-10-18  2:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-17 23:24 [binutils-gdb] Fix duplicate test message in mi-trace-save.exp sergiodj+buildbot
2016-10-18  9:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-25  5:31 [binutils-gdb] ARM/BFD: Correct an `index' global shadowing error sergiodj+buildbot
2016-10-25 20:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-26 16:05 [binutils-gdb] gdb: Clean up remote.c:remote_resume sergiodj+buildbot
2016-10-26 18:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-10-26 20:33 [binutils-gdb] gdb: Free inferior->priv when inferior exits sergiodj+buildbot
2016-11-04 22:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-01 17:00 [binutils-gdb] Add support for RISC-V architecture sergiodj+buildbot
2016-11-08 23:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 15:14 [binutils-gdb] GDBARCH_BREAKPOINT_MANIPULATION and SET_GDBARCH_BREAKPOINT_MANIPULATION sergiodj+buildbot
2016-11-10  2:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 15:40 [binutils-gdb] New gdbarch methods breakpoint_kind_from_pc and sw_breakpoint_from_kind sergiodj+buildbot
2016-11-10 13:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 15:46 [binutils-gdb] Rename placed_size to kind sergiodj+buildbot
2016-11-10 13:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 15:50 [binutils-gdb] Remove gdbarch_remote_breakpoint_from_pc sergiodj+buildbot
2016-11-10 13:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 16:05 [binutils-gdb] Add default_breakpoint_from_pc sergiodj+buildbot
2016-11-10 13:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 16:16 [binutils-gdb] Determine the kind of single step breakpoint sergiodj+buildbot
2016-11-10 13:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 16:26 [binutils-gdb] Remove arm_override_mode sergiodj+buildbot
2016-11-10 13:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 16:27 [binutils-gdb] Remove GDBARCH_BREAKPOINT_MANIPULATION and SET_GDBARCH_BREAKPOINT_MANIPULATION sergiodj+buildbot
2016-11-10 13:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 16:43 [binutils-gdb] X86: Rename REG_82 to REG_83 sergiodj+buildbot
2016-11-10 13:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 16:59 [binutils-gdb] Deprecate old platforms sergiodj+buildbot
2016-11-10 13:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 17:04 [binutils-gdb] Replace YY_NULL with YY_NULLPTR in LANG-exp.c sergiodj+buildbot
2016-11-10 13:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 17:21 [binutils-gdb] X86: Decode opcode 0x82 as opcode 0x80 in 32-bit mode sergiodj+buildbot
2016-11-10 13:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 17:33 [binutils-gdb] X86: Reuse opcode 0x80 decoder for opcode 0x82 sergiodj+buildbot
2016-11-10 13:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 17:39 [binutils-gdb] arc/opcodes/nps400: Fix some instruction masks sergiodj+buildbot
2016-11-10 13:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 17:51 [binutils-gdb] arc: Replace ARC_SHORT macro with arc_opcode_len function sergiodj+buildbot
2016-11-10 13:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 18:03 [binutils-gdb] opcodes/arc: Make some macros 64-bit safe sergiodj+buildbot
2016-11-10 13:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 18:15 [binutils-gdb] arc: Swap highbyte and lowbyte in print_insn_arc sergiodj+buildbot
2016-11-10 13:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 18:26 [binutils-gdb] arc: Change max instruction length to 64-bits sergiodj+buildbot
2016-11-10 13:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 18:59 [binutils-gdb] arc: Implement NPS-400 dcmac instruction sergiodj+buildbot
2016-11-10 13:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 23:05 [binutils-gdb] Fix handling of discriminantless univariant enums in Rust; fix bug with encoded enums sergiodj+buildbot
2016-11-10 13:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 23:17 [binutils-gdb] Add support for untagged unions in Rust sergiodj+buildbot
2016-11-10 13:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-03 23:26 [binutils-gdb] Add support for the sizeof function in Rust sergiodj+buildbot
2016-11-10 13:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-04 14:52 [binutils-gdb] Fix building binutils for all 32-bit targets by moving riscv32 target into 64-bit builds only sergiodj+buildbot
2016-11-10 13:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-04 17:12 [binutils-gdb] Add support for ARM Cortex-M33 processor sergiodj+buildbot
2016-11-10 13:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-04 23:14 [binutils-gdb] arc/nps400: Validate address type operands correctly sergiodj+buildbot
2016-11-10 13:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-05  4:41 [binutils-gdb] Fix a few typos sergiodj+buildbot
2016-11-11  6:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-08  0:39 [binutils-gdb] i386-tdep.c (i386_gdbarch_init): Add comments sergiodj+buildbot
2016-11-12  0:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-08  2:27 [binutils-gdb] X86: Properly handle bad FPU opcode sergiodj+buildbot
2016-11-12 10:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-08 14:37 [binutils-gdb] Remove arm_insert_single_step_breakpoint sergiodj+buildbot
2016-11-13  7:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-08 17:10 [binutils-gdb] gdbarch software_single_step returns VEC (CORE_ADDR) * sergiodj+buildbot
2016-11-13 16:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-08 18:27 [binutils-gdb] breakpoint.c:commands_command_1 constification and cleanup sergiodj+buildbot
2016-11-14  6:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-08 19:48 [binutils-gdb] cli/cli-script.c: Remove some dead NULL checks sergiodj+buildbot
2016-11-14  2:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-08 23:42 [binutils-gdb] Use ui_file_as_string in gdb/xtensa-tdep.c sergiodj+buildbot
2016-11-15  6:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-09  3:33 [binutils-gdb] Use ui_file_as_string in gdb/arm-tdep.c sergiodj+buildbot
2016-11-15 22:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-09  9:53 [binutils-gdb] Use ui_file_as_string in gdb/cli/cli-setshow.c sergiodj+buildbot
2016-11-17  8:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-09 12:46 [binutils-gdb] Use ui_file_as_string in gdbarch.sh/gdbarch.c sergiodj+buildbot
2016-11-17 20:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-09 18:42 [binutils-gdb] Eliminate agent_expr_p; VEC -> std::vector in struct bp_target_info sergiodj+buildbot
2016-11-19  2:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-09 23:16 [binutils-gdb] X86: Remove the THREE_BYTE_0F7A entry sergiodj+buildbot
2016-11-20  2:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-10  3:59 [binutils-gdb] tui-winsource: Allocate for actual lines only sergiodj+buildbot
2016-11-20 18:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-10  7:45 [binutils-gdb] agent_expr_up: gdb::unique_ptr -> std::unique_ptr sergiodj+buildbot
2016-11-21  8:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-10  7:46 [binutils-gdb] Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix sergiodj+buildbot
2016-11-21 16:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-10  9:30 [binutils-gdb] [AArch64] Bind defined symbol locally in PIE sergiodj+buildbot
2016-11-22 14:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11  9:01 [binutils-gdb] sim: mips: fix builds for r3900 cpus due to missing check_u64 sergiodj+buildbot
2016-11-23  7:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 10:09 [binutils-gdb] sim: mips: fix dv-tx3904cpu build error sergiodj+buildbot
2016-11-23 11:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 10:40 [binutils-gdb] Remove parameter valaddr from c print functions sergiodj+buildbot
2016-11-23 15:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 12:02 [binutils-gdb] Remove apply_val_pretty_printer parameter valaddr sergiodj+buildbot
2016-11-23 17:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 12:40 [binutils-gdb] Accept hidden COFF symbols, but treat them as if they were debugging symbols sergiodj+buildbot
2016-11-23 21:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 13:30 [binutils-gdb] [AArch64] Add ARMv8.3 command line option and feature flag sergiodj+buildbot
2016-11-24  1:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 14:42 [binutils-gdb] [AArch64] Increase max_num_aliases in aarch64-gen sergiodj+buildbot
2016-11-24  3:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 15:42 [binutils-gdb] [AArch64] Add ARMv8.3 instructions which are in the NOP space sergiodj+buildbot
2016-11-24  8:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 16:38 [binutils-gdb] [AArch64] Add ARMv8.3 pointer authentication key registers sergiodj+buildbot
2016-11-24 11:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 17:32 [binutils-gdb] [AArch64] Add ARMv8.3 single source PAC instructions sergiodj+buildbot
2016-11-24 14:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 18:47 [binutils-gdb] [AArch64] Add ARMv8.3 PACGA instruction sergiodj+buildbot
2016-11-24 17:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 19:33 [binutils-gdb] [AArch64] Add ARMv8.3 combined pointer authentication branch instructions sergiodj+buildbot
2016-11-24 20:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 20:35 [binutils-gdb] Identify verilog dump tests as such sergiodj+buildbot
2016-11-25  0:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-11 21:18 [binutils-gdb] Don't handle unavailable/optimized-out in spu_software_single_step sergiodj+buildbot
2016-11-25  4:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-12 19:05 [binutils-gdb] Use std::string in rust_get_disr_info sergiodj+buildbot
2016-11-25  7:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-12 20:45 [binutils-gdb] Remove some cleanups from the rust code sergiodj+buildbot
2016-11-25 10:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-14  9:18 [binutils-gdb] Fix typo "Faal through" should be "Fall through" sergiodj+buildbot
2016-11-26  3:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-14 10:28 [binutils-gdb] btrace: read entire aux buffer sergiodj+buildbot
2016-11-26  5:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-14 19:27 [binutils-gdb] Also check GOT PLT for R_X86_64_PLTOFF64 sergiodj+buildbot
2016-11-26 10:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-15 20:24 [binutils-gdb] bitfield-parent-optimized-out: Fix struct definition sergiodj+buildbot
2016-11-26 15:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-15 20:54 [binutils-gdb] gdb::{unique_ptr,move} -> std::{unique_ptr,move} sergiodj+buildbot
2016-11-26 15:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-15 22:01 [binutils-gdb] Delete gdb::unique_ptr/gdb::move sergiodj+buildbot
2016-11-26 19:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-16  0:24 [binutils-gdb] gdb: update gnulib to pull in C++ namespace support fixes sergiodj+buildbot
2016-11-26 22:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-16 20:01 [binutils-gdb] Fix PR20789 - relaxation with negative valued diff relocs sergiodj+buildbot
2016-11-27  2:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-16 20:03 [binutils-gdb] Extend test gdb.python/py-recurse-unwind.exp sergiodj+buildbot
2016-11-28 16:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-16 21:50 [binutils-gdb] Distinguish sentinel frame from null frame sergiodj+buildbot
2016-11-28 19:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-16 22:04 [binutils-gdb] Change meaning of VALUE_FRAME_ID; rename to VALUE_NEXT_FRAME_ID sergiodj+buildbot
2016-11-28 23:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-16 22:59 [binutils-gdb] Make gdb.PendingFrame.read_register handle "user" registers sergiodj+buildbot
2016-11-29  3:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-17  0:20 [binutils-gdb] Stash frame id of current frame before stashing frame id for previous frame sergiodj+buildbot
2016-11-29  6:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-17  1:28 [binutils-gdb] gdb/tracepoint.c: Don't use printf_vma sergiodj+buildbot
2016-11-29 11:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-17 14:41 [binutils-gdb] gdb/ada-lang.c: one malloc -> unique_ptr<[]> sergiodj+buildbot
2016-11-29 12:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-17 15:56 [binutils-gdb] gdb/ctf.c: Get rid of mkdir redefinition sergiodj+buildbot
2016-11-29 17:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-17 16:49 [binutils-gdb] gdb/c-exp.y: fprintf -> parser_fprintf sergiodj+buildbot
2016-11-29 19:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-17 18:31 [binutils-gdb] Document new hard requirement on GNU make sergiodj+buildbot
2016-11-29 23:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-17 18:49 [binutils-gdb] Remove code that checks for GNU/non-GNU make sergiodj+buildbot
2016-11-30  3:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-17 19:35 [binutils-gdb] Makefile: Replace old suffix rules with pattern rules sergiodj+buildbot
2016-11-30  4:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-17 20:10 [binutils-gdb] Makefile: Replace explicit subdir rules with pattern rules sergiodj+buildbot
2016-11-30  6:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18  9:59 [binutils-gdb] Help diagnose problems with the metag target when mixing static and shared binaries sergiodj+buildbot
2016-11-30 10:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 11:23 [binutils-gdb] [AArch64] Add ARMv8.3 combined pointer authentication load instructions sergiodj+buildbot
2016-11-30 12:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 11:34 [binutils-gdb] [AArch64] Add ARMv8.3 javascript floating-point conversion instruction sergiodj+buildbot
2016-11-30 16:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 12:49 [binutils-gdb] [AArch64] Add ARMv8.3 weaker release consistency load instructions sergiodj+buildbot
2016-11-30 19:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 13:05 [binutils-gdb] [AArch64] Add ARMv8.3 FCMLA and FCADD instructions sergiodj+buildbot
2016-11-30 21:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 14:01 [binutils-gdb] PR c++/71696 testcase sergiodj+buildbot
2016-12-01  0:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 16:06 [binutils-gdb] Implement P0136R1, Rewording inheriting constructors sergiodj+buildbot
2016-12-01  5:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 16:14 [binutils-gdb] libiberty: Fix -Wimplicit-fallthrough warnings sergiodj+buildbot
2016-12-01  9:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 16:19 [binutils-gdb] libiberty: Fix memory leak in ada_demangle when symbol cannot be demangled sergiodj+buildbot
2016-12-01  3:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 16:45 [binutils-gdb] Implement P0012R1, Make exception specifications part of the type system sergiodj+buildbot
2016-12-01 11:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 18:01 [binutils-gdb] libiberty: Add -Wshadow=local to warning flags (if supported) sergiodj+buildbot
2016-12-01 15:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 18:18 [binutils-gdb] libiberty: Fix some demangler crashes caused by reading past end of input sergiodj+buildbot
2016-12-01 17:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-18 19:31 [binutils-gdb] libiberty: Add Rust symbol demangling sergiodj+buildbot
2016-12-01 23:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-19  0:43 [binutils-gdb] bfd: fix negative GOT offsets for non-local references on sparc64 sergiodj+buildbot
2016-12-02  2:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-19  1:25 [binutils-gdb] libiberty: demangler crash with missing :? or fold expression component sergiodj+buildbot
2016-12-01 21:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-19  3:34 [binutils-gdb] Makefile: fix typo sergiodj+buildbot
2016-12-02  5:17 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-19 13:29 [binutils-gdb] Revert "bfd: allow negative offsets to _GLOBAL_OFFSET_TABLE_ in elf64 SPARC" sergiodj+buildbot
2016-12-02  8:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-19 19:14 [binutils-gdb] ARI: Add detection of printf_vma and sprintf_vma sergiodj+buildbot
2016-12-02 10:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-21 14:37 [binutils-gdb] Create subobject value in pretty printer sergiodj+buildbot
2016-12-02 21:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-21 17:38 [binutils-gdb] BFD/DWARF2: Correct an `index' global shadowing error sergiodj+buildbot
2016-12-03  0:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-21 21:38 [binutils-gdb] Add missing POSTCOMPILE step to mi/ file generation rules sergiodj+buildbot
2016-12-03  4:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 10:10 [binutils-gdb] Use VALUE_NEXT_FRAME_ID in value_from_component sergiodj+buildbot
2016-12-03  6:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 10:39 [binutils-gdb] Use input_bfd in relocate_section sergiodj+buildbot
2016-12-03  9:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 11:18 [binutils-gdb] PR20744, Incorrect PowerPC VLE relocs sergiodj+buildbot
2016-12-03 11:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 13:53 [binutils-gdb] gas, opcodes: fix hardware capabilities bumping in the sparc assembler sergiodj+buildbot
2016-12-03 17:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 14:50 [binutils-gdb] [ARC] Fix printing 'b' mnemonics sergiodj+buildbot
2016-12-03 13:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 15:10 [binutils-gdb] New regcache_raw_get_signed sergiodj+buildbot
2016-12-03 21:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 15:55 [binutils-gdb] gdbarch software_single_step frame_info to regcache: aarch64 sergiodj+buildbot
2016-12-04  0:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 16:56 [binutils-gdb] gdbarch software_single_step frame_info to regcache: alpha sergiodj+buildbot
2016-12-04  1:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 17:26 [binutils-gdb] gdbarch software_single_step frame_info to regcache: cris sergiodj+buildbot
2016-12-04  6:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 17:49 [binutils-gdb] gdbarch software_single_step frame_info to regcache: mips sergiodj+buildbot
2016-12-04  8:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 18:47 [binutils-gdb] gdbarch software_single_step frame_info to regcache: moxie sergiodj+buildbot
2016-12-04 11:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 19:25 [binutils-gdb] gdbarch software_single_step frame_info to regcache: nios2 sergiodj+buildbot
2016-12-04 14:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 20:15 [binutils-gdb] gdbarch software_single_step frame_info to regcache: sparc sergiodj+buildbot
2016-12-04 17:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 20:47 [binutils-gdb] gdbarch software_single_step frame_info to regcache: s390 sergiodj+buildbot
2016-12-04 22:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 21:00 [binutils-gdb] gdbarch software_single_step frame_info to regcache: rs6000 sergiodj+buildbot
2016-12-05  2:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-22 22:40 [binutils-gdb] gdbarch software_single_step frame_info to regcache: spu sergiodj+buildbot
2016-12-05  4:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23  0:03 [binutils-gdb] Change gdbarch software_single_step frame_info to regcache sergiodj+buildbot
2016-12-05  6:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23  0:36 [binutils-gdb] gdbarch software_single_step frame_info to regcache: tic6x sergiodj+buildbot
2016-12-05  2:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23  1:00 [binutils-gdb] Fix spelling mistakes in comments in shell scripts sergiodj+buildbot
2016-12-05 12:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23  1:51 [binutils-gdb] gdbserver: Use debug_printf for debug output sergiodj+buildbot
2016-12-05 15:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23  2:43 [binutils-gdb] gdbserver: Use warning for warnings sergiodj+buildbot
2016-12-05 18:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23  3:21 [binutils-gdb] Fix spelling mistakes in comments in configure scripts sergiodj+buildbot
2016-12-05 11:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23  7:46 [binutils-gdb] Regen POTFILES.in sergiodj+buildbot
2016-12-05 22:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23  8:40 [binutils-gdb] Delete duplicate target short-cuts to dynamic sections sergiodj+buildbot
2016-12-06  1:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23  9:06 [binutils-gdb] elf_backend_dtrel_excludes_plt sergiodj+buildbot
2016-12-06  5:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23 11:55 [binutils-gdb] Fix the linker so that it will not silently generate ELF binaries with invalid program headers. Fix readelf to report such invalid binaries sergiodj+buildbot
2016-12-06  6:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23 15:19 [binutils-gdb] Makefiles: Flatten and sort file lists sergiodj+buildbot
2016-12-06 10:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23 16:36 [binutils-gdb] Normalize names of some source files sergiodj+buildbot
2016-12-06 14:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23 17:10 [binutils-gdb] Minor formatting fixups in Makefiles sergiodj+buildbot
2016-12-06 15:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-23 17:24 [binutils-gdb] gdb: Use C++11 std::chrono sergiodj+buildbot
2016-12-06 18:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-24  3:59 [binutils-gdb] RISC-V/bfd: Fix bitsize of R_RISCV_ADD8 sergiodj+buildbot
2016-12-06 21:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-24 14:48 [binutils-gdb] [ARM] Bind defined symbol locally in PIE sergiodj+buildbot
2016-12-07  3:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-24 17:53 [binutils-gdb] Fix PR12616 - gdb does not implement DW_AT_data_bit_offset sergiodj+buildbot
2016-12-07  5:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-24 18:47 [binutils-gdb] Fix copy_bitwise() sergiodj+buildbot
2016-12-07  9:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-24 19:13 [binutils-gdb] Add unit test for copy_bitwise sergiodj+buildbot
2016-12-07 10:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-24 19:17 [binutils-gdb] Optimize byte-aligned copies in copy_bitwise() sergiodj+buildbot
2016-12-07 12:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-24 21:00 [binutils-gdb] Add noexcept to custom non-throwing new operators sergiodj+buildbot
2016-12-07 15:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-24 21:27 [binutils-gdb] Do not use std::move when assigning an anonymous object to a unique_ptr sergiodj+buildbot
2016-12-07 19:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-25 10:36 [binutils-gdb] Prevent problems with section alignment by not shrinking the .rsrc section sergiodj+buildbot
2016-12-07 22:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-25 15:36 [binutils-gdb] Fix typos in comment sergiodj+buildbot
2016-12-08  4:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-25 16:29 [binutils-gdb] Fix typo in comment sergiodj+buildbot
2016-12-08  2:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-25 17:47 [binutils-gdb] Fix typo in Makefile sergiodj+buildbot
2016-12-08  7:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-25 21:27 [binutils-gdb] Remove check requiring void argument to functions with no parameters sergiodj+buildbot
2016-12-08 10:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-26 15:59 [binutils-gdb] Remove stale comments sergiodj+buildbot
2016-12-08 12:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-27  4:20 [binutils-gdb] Remove unused functions and declarations sergiodj+buildbot
2016-12-08 15:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-27  4:37 [binutils-gdb] Rename ui_out_data to mi_ui_out_data sergiodj+buildbot
2016-12-08 19:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-27  5:37 [binutils-gdb] Remove ui_out_destroy sergiodj+buildbot
2016-12-08 22:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-27  5:56 [binutils-gdb] Fix return value of uo_redirect sergiodj+buildbot
2016-12-09  0:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-27  8:16 [binutils-gdb] Constify wrap_here/wrap_hint code path sergiodj+buildbot
2016-12-09  4:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-27  8:30 [binutils-gdb] Remove verbosity from ui_out_message and friends sergiodj+buildbot
2016-12-09  6:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-28 16:35 [binutils-gdb] Properly hide hidden versioned symbol in executable sergiodj+buildbot
2016-12-09 17:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-28 17:50 [binutils-gdb] Move computed value's frame id to piece_closure sergiodj+buildbot
2016-12-09 20:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-28 19:26 [binutils-gdb] Adjust Value.location for lval_register sergiodj+buildbot
2016-12-09 23:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-28 19:38 [binutils-gdb] Restrict checking value.lval on using address sergiodj+buildbot
2016-12-10  3:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-28 20:51 [binutils-gdb] Partially revert patch for PR 20815 - do not sort the PT_LOAD segments. Non-ordered segments are needed by the Linux kernel sergiodj+buildbot
2016-12-10  8:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-28 21:09 [binutils-gdb] X86: Ignore REX_B bit for 32-bit XOP instructions sergiodj+buildbot
2016-12-10  5:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-29  3:18 [binutils-gdb] Fix debug output in record_full_open_1 sergiodj+buildbot
2016-12-10 12:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-29 11:20 [binutils-gdb] [ARC] Fix disassembler option sergiodj+buildbot
2016-12-10 15:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-29 12:01 [binutils-gdb] [ARC] Add checking for LP_COUNT reg usage, improve error reporting sergiodj+buildbot
2016-12-10 17:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-30  7:01 [binutils-gdb] PR20886, looping in ppc64_elf_size_stubs sergiodj+buildbot
2016-12-10 20:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-30 12:13 [binutils-gdb] Revert accidental elf.c change sergiodj+buildbot
2016-12-11  3:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-30 12:39 [binutils-gdb] [ARM] Read memory as unsigned integer sergiodj+buildbot
2016-12-11  5:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-11-30 21:56 [binutils-gdb] Makefiles: Disable suffix rules and implicit rules sergiodj+buildbot
2016-12-11  8:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01  3:08 [binutils-gdb] Use new/delete instead of malloc/free-based functions sergiodj+buildbot
2016-12-11 10:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01  3:47 [binutils-gdb] Use std::vector for ui_out::levels sergiodj+buildbot
2016-12-11 15:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01  4:21 [binutils-gdb] Use std::vector for mi_ui_out_data::streams sergiodj+buildbot
2016-12-11 19:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01  5:08 [binutils-gdb] Use std::vector for cli_ui_out_data::streams sergiodj+buildbot
2016-12-11 20:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01  5:58 [binutils-gdb] Use std::string in ui_out_table sergiodj+buildbot
2016-12-11 22:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 10:32 [binutils-gdb] Fix seg-fault running addr2line on a corrupt binary sergiodj+buildbot
2016-12-12  1:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 12:11 [binutils-gdb] Fix abort in x86 disassembler sergiodj+buildbot
2016-12-12  4:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 12:29 [binutils-gdb] Fix a seg-fault disassembling a corrupt binary sergiodj+buildbot
2016-12-12  7:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 13:18 [binutils-gdb] Fix handling of MIPS16 HI16 relocs sergiodj+buildbot
2016-12-12 10:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 14:12 [binutils-gdb] Fix accesses to the GOT for AARCH64 operating in 32-bit mode sergiodj+buildbot
2016-12-12 13:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 17:48 [binutils-gdb] Fix bug with FP stur instructions sergiodj+buildbot
2016-12-12 18:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 21:12 [binutils-gdb] Fix test names starting with uppercase output by basic functions sergiodj+buildbot
2016-12-12 20:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 21:50 [binutils-gdb] Fix test names starting with uppercase using gdb_test on a single line sergiodj+buildbot
2016-12-12 23:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 22:09 [binutils-gdb] Fix test names starting with uppercase using gdb_test_no_output sergiodj+buildbot
2016-12-13  2:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 23:01 [binutils-gdb] Fix test names starting with uppercase using gdb_test_multiple sergiodj+buildbot
2016-12-13  5:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-01 23:25 [binutils-gdb] Fix test names starting with uppercase using multi-line gdb_test/mi_gdb_test sergiodj+buildbot
2016-12-13  8:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  0:06 [binutils-gdb] Fix test names starting with uppercase using multi-line gdb_test_no_output sergiodj+buildbot
2016-12-13 11:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  0:34 [binutils-gdb] Fix test names starting with uppercase using multi-line gdb_test_multiple sergiodj+buildbot
2016-12-13 13:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  1:27 [binutils-gdb] Fixup testcases outputting own name as a test name and standardize failed compilation messages sergiodj+buildbot
2016-12-13 17:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  2:11 [binutils-gdb] Replace hand-made linked list of ui_out_hdr by vector and iterator sergiodj+buildbot
2016-12-13 20:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  2:20 [binutils-gdb] Use std::string for ui_out_hdr's text fields sergiodj+buildbot
2016-12-13 22:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  2:49 [binutils-gdb] Class-ify ui_out_hdr sergiodj+buildbot
2016-12-14  1:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  3:57 [binutils-gdb] Class-ify ui_out_level sergiodj+buildbot
2016-12-14  4:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  4:41 [binutils-gdb] Simplify ui-out level code sergiodj+buildbot
2016-12-14  6:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  5:00 [binutils-gdb] ui_out_table: Replace boolean flag with enum sergiodj+buildbot
2016-12-14  9:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  5:34 [binutils-gdb] Class-ify ui_out_table sergiodj+buildbot
2016-12-14 12:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02  6:01 [binutils-gdb] Don't handle timeout inside gdb_test_multiple sergiodj+buildbot
2016-12-14 17:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 10:11 [binutils-gdb] Add unit test to aarch64 prologue analyzer sergiodj+buildbot
2016-12-14 21:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 10:50 [binutils-gdb] [AArch64] Recognize STR instruction in prologue sergiodj+buildbot
2016-12-14 22:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 11:30 [binutils-gdb] Add support for Fushia OS sergiodj+buildbot
2016-12-15  1:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 12:02 [binutils-gdb] Always pass a valid section header offset to elf_parse_notes sergiodj+buildbot
2016-12-15  4:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 15:26 [binutils-gdb] Remove mi_out_data::suppress_output sergiodj+buildbot
2016-12-15  8:19 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 16:03 [binutils-gdb] Rename some trace functions sergiodj+buildbot
2016-12-15 12:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 16:48 [binutils-gdb] PR symtab/16264 - support DW_AT_main_subprogram sergiodj+buildbot
2016-12-15 13:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 17:12 [binutils-gdb] Fix seg-fault in the linker when examining a corrupt binary sergiodj+buildbot
2016-12-15 17:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 18:11 [binutils-gdb] Revert change to gdb.cp/ovldbreak.exp sergiodj+buildbot
2016-12-15 20:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 18:56 [binutils-gdb] Fix seg-fault in linker when passed a corrupt binary input file sergiodj+buildbot
2016-12-15 23:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 19:55 [binutils-gdb] Fix PR 20559 - "eval" command and $arg0...$arg9/$argc substitution sergiodj+buildbot
2016-12-16  2:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 20:34 [binutils-gdb] Test user-defined gdb commands and arguments stack sergiodj+buildbot
2016-12-16  3:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 21:13 [binutils-gdb] Support an "unlimited" number of user-defined arguments sergiodj+buildbot
2016-12-16  7:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 21:50 [binutils-gdb] Remove unneeded pattern matching in gdb.base/maint.exp sergiodj+buildbot
2016-12-16 11:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-02 22:35 [binutils-gdb] Introduce enum_flag type for ui_out flags sergiodj+buildbot
2016-12-16 12:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-03 11:13 [binutils-gdb] ppc64_elf_copy_indirect_symbol versioned_hidden fix sergiodj+buildbot
2016-12-16 16:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-03 11:55 [binutils-gdb] Indirect and warning symbols sergiodj+buildbot
2016-12-16 18:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-03 12:21 [binutils-gdb] PowerPC64 add_symbol_adjust sergiodj+buildbot
2016-12-16 22:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-03 13:02 [binutils-gdb] Tidy ppc64_elf_hide_symbol sergiodj+buildbot
2016-12-17  3:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-03 13:35 [binutils-gdb] PowerPC64 dot-symbol compatibility bugfixes sergiodj+buildbot
2016-12-17  6:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-04  2:02 [binutils-gdb] Fix bugs with tbnz/tbz instructions sergiodj+buildbot
2016-12-17 14:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <@gdb-build>
2016-12-17 14:40 ` sergiodj+buildbot
2016-12-17 15:08 ` sergiodj+buildbot
2016-12-17 16:20 ` sergiodj+buildbot
2016-12-17 18:42 ` sergiodj+buildbot
2016-12-17 19:43 ` sergiodj+buildbot
2016-12-17 22:59 ` sergiodj+buildbot
2016-12-17 23:51 ` sergiodj+buildbot
2016-12-18  0:49 ` sergiodj+buildbot
2016-12-18  2:28 ` sergiodj+buildbot
2016-12-18  4:09 ` sergiodj+buildbot
2016-12-18  6:34 ` sergiodj+buildbot
2016-12-18  6:52 ` sergiodj+buildbot
2016-12-18 10:54 ` sergiodj+buildbot
2016-12-18 11:41 ` sergiodj+buildbot
2016-12-18 12:36 ` sergiodj+buildbot
2016-12-18 14:32 ` sergiodj+buildbot
2016-12-18 15:47 ` sergiodj+buildbot
2016-12-18 18:19 ` sergiodj+buildbot
2016-12-18 19:24 ` sergiodj+buildbot
2016-12-18 21:07 ` sergiodj+buildbot
2016-12-18 22:49 ` sergiodj+buildbot
2016-12-19  0:29 ` sergiodj+buildbot
2016-12-19  2:17 ` sergiodj+buildbot
2016-12-19  4:10 ` sergiodj+buildbot
2016-12-19  5:38 ` sergiodj+buildbot
2016-12-19  6:44 ` sergiodj+buildbot
2016-12-19  9:56 ` sergiodj+buildbot
2016-12-19 11:12 ` sergiodj+buildbot
2016-12-19 11:44 ` sergiodj+buildbot
2016-12-19 13:05 ` sergiodj+buildbot
2016-12-19 15:05 ` sergiodj+buildbot
2016-12-19 17:42 ` sergiodj+buildbot
2016-12-19 19:54 ` sergiodj+buildbot
2016-12-19 21:07 ` sergiodj+buildbot
2016-12-19 23:05 ` sergiodj+buildbot
2016-12-19 23:54 ` sergiodj+buildbot
2016-12-20  2:02 ` sergiodj+buildbot
2016-12-20  2:41 ` sergiodj+buildbot
2016-12-20  5:37 ` sergiodj+buildbot
2016-12-20  6:23 ` sergiodj+buildbot
2016-12-20  9:31 ` sergiodj+buildbot
2016-12-20 10:55 ` sergiodj+buildbot
2016-12-20 11:53 ` sergiodj+buildbot
2016-12-20 17:36 ` sergiodj+buildbot
2016-12-20 18:35 ` sergiodj+buildbot
2016-12-20 19:55 ` sergiodj+buildbot
2016-12-20 21:39 ` sergiodj+buildbot
2016-12-21  1:26 ` sergiodj+buildbot
2016-12-21  2:27 ` sergiodj+buildbot
2016-12-21  2:53 ` sergiodj+buildbot
2016-12-21  8:37 ` sergiodj+buildbot
2016-12-21 11:19 ` sergiodj+buildbot
2016-12-21 11:33 ` sergiodj+buildbot
2016-12-21 11:33 ` sergiodj+buildbot
2016-12-21 13:07 ` sergiodj+buildbot
2016-12-21 14:27 ` sergiodj+buildbot
2016-12-21 16:42 ` sergiodj+buildbot
2016-12-21 19:48 ` sergiodj+buildbot
2016-12-21 20:45 ` sergiodj+buildbot
2016-12-21 20:51 ` sergiodj+buildbot
2016-12-21 20:53 ` sergiodj+buildbot
2016-12-22  0:23 ` sergiodj+buildbot
2016-12-22  2:09 ` sergiodj+buildbot
2016-12-22  3:31 ` sergiodj+buildbot
2016-12-22  4:52 ` sergiodj+buildbot
2016-12-22  6:36 ` sergiodj+buildbot
2016-12-22  6:58 ` sergiodj+buildbot
2016-12-22  7:37 ` sergiodj+buildbot
2016-12-22 11:46 ` sergiodj+buildbot
2016-12-22 13:08 ` sergiodj+buildbot
2016-12-22 15:52 ` sergiodj+buildbot
2016-12-22 17:13 ` sergiodj+buildbot
2016-12-22 18:34 ` sergiodj+buildbot
2016-12-22 19:15 ` sergiodj+buildbot
2016-12-22 21:19 ` sergiodj+buildbot
2016-12-22 21:24 ` sergiodj+buildbot
2016-12-20  2:06 [binutils-gdb] Correct assembler mnemonic for RISC-V aqrl AMOs sergiodj+buildbot
2016-12-23 21:24 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-20 14:09 [binutils-gdb] MIPS16/opcodes: Correct 64-bit macros' ISA membership sergiodj+buildbot
2016-12-24  4:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-20 15:08 [binutils-gdb] MIPS16/opcodes: Respect ISA and ASE in disassembly sergiodj+buildbot
2016-12-24 13:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-21 14:46 [binutils-gdb] Avoid creating symbol table entries for registers sergiodj+buildbot
2016-12-25 17:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-21 15:21 [binutils-gdb] Don't make_bfd_vms_lib archive functions NULL sergiodj+buildbot
2016-12-25 20:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-23 12:50 [binutils-gdb] Updated email address sergiodj+buildbot
2016-12-27  6:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-23 20:03 [binutils-gdb] Fix more cases of improper test names sergiodj+buildbot
2016-12-28  3:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-23 21:34 [binutils-gdb] MIPS16/GAS: Disallow EXTEND delay-slot scheduling sergiodj+buildbot
2016-12-28 12:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-23 22:22 [binutils-gdb] MIPS16: Simplify extended operand handling sergiodj+buildbot
2016-12-29  3:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-24  0:33 [binutils-gdb] MIPS16: Reassign `0' and `4' operand codes sergiodj+buildbot
2016-12-29  0:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-24  3:33 [binutils-gdb] MIPS/BFD: Remove EI_ABIVERSION 5 allocation for PT_GNU_STACK support sergiodj+buildbot
2016-12-29 13:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-26  6:54 [binutils-gdb] dynrelro section for read-only dynamic symbols copied into executable sergiodj+buildbot
2016-12-30  1:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-28 13:44 [binutils-gdb] Check bfd support for bfd_mips_elf_get_abiflags in mips make rule sergiodj+buildbot
2016-12-30 12:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-31  4:19 [binutils-gdb] PRU Opcode Port sergiodj+buildbot
2016-12-31 15:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2016-12-31  9:11 [binutils-gdb] Create sdynrelro for elfn32 mips too sergiodj+buildbot
2016-12-31 19:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-04  1:22 [binutils-gdb] Don't make symbols dynamic other than undef weak sergiodj+buildbot
2017-01-04 11:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-04  1:38 [binutils-gdb] Fix compile time warning about using a possibly uninitialised variable sergiodj+buildbot
2017-01-04 23:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-04  2:06 [binutils-gdb] Regen opcodes cgen files sergiodj+buildbot
2017-01-04 15:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-04  3:11 [binutils-gdb] Add fall through comment sergiodj+buildbot
2017-01-05  7:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-04  3:42 [binutils-gdb] Add support for the Q extension to the RISCV ISA sergiodj+buildbot
2017-01-05 14:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-04  3:56 [binutils-gdb] bfd: alpha: Fix crash caused by double free with --no-keep-memory sergiodj+buildbot
2017-01-05 18:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-04 10:10 [binutils-gdb] Fix an internal error on writing pieced value sergiodj+buildbot
2017-01-05 22:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-04 14:42 [binutils-gdb] Sync libiberty from gcc sergiodj+buildbot
2017-01-06 10:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-04 14:57 [binutils-gdb] update-copyright.py for binutils sergiodj+buildbot
2017-01-06 14:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-04 20:32 [binutils-gdb] Use correct OSABI constant for FreeBSD/mips binaries sergiodj+buildbot
2017-01-06 22:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-05  0:23 [binutils-gdb] Five fixes, for fcsel, fcvtz, fminnm, mls, and non-widening mul sergiodj+buildbot
2017-01-07  3:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-05  9:19 [binutils-gdb] Prevent an abort in the FRV disassembler if the target bfd name is unknown sergiodj+buildbot
2017-01-07  7:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-05 15:02 [binutils-gdb] Fix ARI warning sergiodj+buildbot
2017-01-07 11:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-06 14:17 [binutils-gdb] Update gdb_ptrace.h in HFILES_NO_SRCDIR sergiodj+buildbot
2017-01-07 15:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-06 15:00 [binutils-gdb] Include ax.h in ax-gdb.h sergiodj+buildbot
2017-01-07 19:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-06 17:58 [binutils-gdb] Include break-common.h in nat/aarch64-linux-hw-point.h sergiodj+buildbot
2017-01-08 11:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-06 19:51 [binutils-gdb] Include serial.h in ser-base.h sergiodj+buildbot
2017-01-08 22:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-06 20:40 [binutils-gdb] Include gdb_proc_service.h in x86-linux-nat.h sergiodj+buildbot
2017-01-09  2:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-08 10:52 [binutils-gdb] [D] Fix crash when debug expression enabled sergiodj+buildbot
2017-01-09 17:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-09 17:05 [binutils-gdb] Speed up objdump when displaying disassembly mixed with line number and source code information sergiodj+buildbot
2017-01-10  0:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-10  0:02 [binutils-gdb] Fix problems with the implementation of the uzp1 and uzp2 instructions sergiodj+buildbot
2017-01-10  7:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-10 16:47 [binutils-gdb] Change return type of ui_out redirect to void sergiodj+buildbot
2017-01-10 20:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-10 19:51 [binutils-gdb] Don't use elf_i386_eh_frame_plt directly sergiodj+buildbot
2017-01-11  1:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11  7:18 [binutils-gdb] Change event code to use gdbpy_ref sergiodj+buildbot
2017-01-11 18:22 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11  7:59 [binutils-gdb] Use gdbpy_ref in py-framefilter.c sergiodj+buildbot
2017-01-12 18:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11  8:42 [binutils-gdb] Use gdbpy_ref in gdbpy_string_to_argv sergiodj+buildbot
2017-01-12  2:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11  9:54 [binutils-gdb] Use gdbpy_ref in call_doc_function sergiodj+buildbot
2017-01-13  3:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11 11:14 [binutils-gdb] Use gdbpy_ref in py-value.c sergiodj+buildbot
2017-01-13 14:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11 11:46 [binutils-gdb] Introduce gdbpy_enter sergiodj+buildbot
2017-01-13 22:48 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11 12:51 [binutils-gdb] Use gdbpy_enter in py-cmd.c sergiodj+buildbot
2017-01-14  7:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11 14:12 [binutils-gdb] Use gdbpy_enter in py-objfile.c sergiodj+buildbot
2017-01-14 20:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11 14:43 [binutils-gdb] Use gdbpy_enter in python.c sergiodj+buildbot
2017-01-15  3:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11 19:03 [binutils-gdb] Use gdbpy_enter in py-xmethod.c sergiodj+buildbot
2017-01-16 18:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-11 19:07 [binutils-gdb] Use gdbpy_enter in py-finishbreakpoint.c sergiodj+buildbot
2017-01-14 11:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-12  5:21 [binutils-gdb] Use gdbpy_ref in invoke_match_method sergiodj+buildbot
2017-01-16 14:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-27  8:31 [binutils-gdb] Fix unused-but-set warning in elf32-cris.c:elf_cris_finish_dynamic_symbol sergiodj+buildbot
2017-01-27 15:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-27 14:35 [binutils-gdb] gdbserver-amd64: add HAVE_STRUCT_USER_REGS_STRUCT_(GS|FS)_BASE for gdbserver sergiodj+buildbot
2017-01-28  4:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-27 15:16 [binutils-gdb] amd64: remove additional comparison for validity of a register number sergiodj+buildbot
2017-01-28  8:07 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-27 16:49 [binutils-gdb] amd64-linux: expose system register FS_BASE and GS_BASE for Linux sergiodj+buildbot
2017-01-28 16:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-01-31 23:53 [binutils-gdb] gdb: make_scoped_restore and types convertible to T sergiodj+buildbot
2017-02-01  1:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-01  0:40 [binutils-gdb] gdb/varobj.c: Fix leak sergiodj+buildbot
2017-02-01  6:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-01 13:56 [binutils-gdb] thread: add can_access_registers_ptid sergiodj+buildbot
2017-02-01 21:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-01 15:06 [binutils-gdb] btrace: add unsupported/untested messages when skipping tests sergiodj+buildbot
2017-02-02  6:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-01 15:42 [binutils-gdb] btrace, testsuite: fix extended-remote non-stop test sergiodj+buildbot
2017-02-02 10:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-01 16:25 [binutils-gdb] Big-endian targets: Don't ignore offset into DW_OP_implicit_value sergiodj+buildbot
2017-02-02 22:12 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-02 12:25 [binutils-gdb] Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy sergiodj+buildbot
2017-02-03  9:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-02 13:57 [binutils-gdb] Tweak pretty_print_disassembler's intro comment sergiodj+buildbot
2017-02-03 17:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-02 14:53 [binutils-gdb] Fix "-gdb-set logging redirect on" crash sergiodj+buildbot
2017-02-03 21:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-02 22:23 [binutils-gdb] Move "tee" building down to interpreter::set_logging_proc sergiodj+buildbot
2017-02-04  1:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-02 23:22 [binutils-gdb] BFD: Wrap overlong error handler call line in `elf_gc_sweep' sergiodj+buildbot
2017-02-04  5:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-02 23:37 [binutils-gdb] MIPS/BFD: Fix assertion in `mips_elf_sort_hash_table' sergiodj+buildbot
2017-02-04  9:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-03  0:13 [binutils-gdb] MIPS/BFD: Respect the ELF gABI dynamic symbol table sort requirement sergiodj+buildbot
2017-02-04 21:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-03  0:38 [binutils-gdb] Fix "maintenance selftest" printing stray instructions sergiodj+buildbot
2017-02-05  5:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-03  1:31 [binutils-gdb] MIPS/BFD: Streamline hash table references in `mips_elf_sort_hash_table' sergiodj+buildbot
2017-02-04 13:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-03  9:19 [binutils-gdb] Fix compile time warning messages when compiling binutils with gcc 7.0.1 sergiodj+buildbot
2017-02-05 22:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-06  9:31 [binutils-gdb] [BZ 21005] Add support for Intel 64 rdrand and rdseed record/replay sergiodj+buildbot
2017-02-06 22:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-06 10:53 [binutils-gdb] [ARC] Provide an interface to decode ARC instructions sergiodj+buildbot
2017-02-07  3:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-07 14:25 [binutils-gdb] bfd: Fix objdump --dynamic-reloc for SPARC 64-bit to show symbol names sergiodj+buildbot
2017-02-07 15:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-07 21:40 [binutils-gdb] gdb: fix ARI warning in sparc-tdep.c sergiodj+buildbot
2017-02-07 23:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-08 18:32 [binutils-gdb] Command names: make them case sensitive sergiodj+buildbot
2017-02-08 20:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-08 20:52 [binutils-gdb] Eliminate interp::quiet_p sergiodj+buildbot
2017-02-09  4:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-09 15:56 [binutils-gdb] Fix NULL pointer dereference sergiodj+buildbot
2017-02-09 17:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-10  8:52 [binutils-gdb] POWER9 add scv/rfscv instruction support sergiodj+buildbot
2017-02-10 10:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-10 18:09 [binutils-gdb] gdb/MAINTAINERS: Update my e-mail address sergiodj+buildbot
2017-02-10 23:02 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-10 20:08 [binutils-gdb] Remove some ui_out-related cleanups from Python sergiodj+buildbot
2017-02-11  4:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-11  0:55 [binutils-gdb] Remove unnecessary local variables sergiodj+buildbot
2017-02-12  0:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-11  5:11 [binutils-gdb] Remove unused variable in rust-lang.c sergiodj+buildbot
2017-02-12  9:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-13 15:27 [binutils-gdb] Improve load command's help text sergiodj+buildbot
2017-02-13 23:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-14 10:42 [binutils-gdb] btrace: Count gaps as one instruction explicitly sergiodj+buildbot
2017-02-14 15:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-14 17:02 [binutils-gdb] python: Implement btrace Python bindings for record history sergiodj+buildbot
2017-02-15 18:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-14 19:24 [binutils-gdb] Update ppc64_elf_gc_mark_dynamic_ref sergiodj+buildbot
2017-02-16  6:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-15 12:11 [binutils-gdb] Fix illegal upper case gdb cmd in chained-calls.exp sergiodj+buildbot
2017-02-17 17:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-15 17:26 [binutils-gdb] [AArch64] Add SVE system registers sergiodj+buildbot
2017-02-18  2:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-15 21:34 [binutils-gdb] i386: Allow "lea foo@GOT, %reg" in PIC sergiodj+buildbot
2017-02-18 13:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-17 11:43 [binutils-gdb] Add support for Intel PKRU register to GDB and GDBserver sergiodj+buildbot
2017-02-21  0:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-20 20:58 [binutils-gdb] Code cleanup: Split dwarf2_ranges_read to a callback sergiodj+buildbot
2017-02-22  0:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-21 14:17 [binutils-gdb] Fix test names starting with uppercase in gdb.arch/ppc64-atomic-inst.exp sergiodj+buildbot
2017-02-22 15:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-21 15:39 [binutils-gdb] [ppc64] Add POWER8/ISA 2.07 atomic sequences single-stepping support sergiodj+buildbot
2017-02-22 20:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-21 23:12 [binutils-gdb] PowerPC ld segfault on script discarding dynamic sections sergiodj+buildbot
2017-02-23  3:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-22 17:45 [binutils-gdb] Align .gnu_debuglink sections on a 4-byte boundary sergiodj+buildbot
2017-02-23 15:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-23 10:18 [binutils-gdb] x86: drop stray VEX opcode 82 references sergiodj+buildbot
2017-02-24  4:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-23 15:54 [binutils-gdb] Fix usage of inferior_ptid in two thread_alive implementations sergiodj+buildbot
2017-02-24 16:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-23 20:15 [binutils-gdb] S/390: Add support for new cpu architecture - arch12 sergiodj+buildbot
2017-02-25  8:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-24 19:18 [binutils-gdb] Add new counter-enable CSRs sergiodj+buildbot
2017-02-26 12:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-26  5:34 [binutils-gdb] Add missing smov support, and clean up existing umov support sergiodj+buildbot
2017-02-27 16:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-27 18:58 [binutils-gdb] Use range-based for loop in remote_add_target_side_condition sergiodj+buildbot
2017-02-28 21:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-28  0:57 [binutils-gdb] MIPS/BFD: Also handle `jalr $0, $25' with R_MIPS_JALR sergiodj+buildbot
2017-03-01  5:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-28  4:22 [binutils-gdb] PowerPC addpcis fix sergiodj+buildbot
2017-03-01 13:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-02-28 10:17 [binutils-gdb] x86: fix handling of 64-bit operand size VPCMPESTR{I, M} sergiodj+buildbot
2017-03-01 22:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-02  0:24 [binutils-gdb] PowerPC VLE typo fix sergiodj+buildbot
2017-03-02 17:18 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-05  4:44 [binutils-gdb] Align eh_frame FDEs according to their encoding sergiodj+buildbot
2017-03-05  6:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-07 14:45 [binutils-gdb] Add describing intro comment to gdb.base/tui-layout.exp sergiodj+buildbot
2017-03-07 18:34 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-07 21:08 [binutils-gdb] Share gdb/environ.[ch] with gdbserver sergiodj+buildbot
2017-03-08 16:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-08  0:56 [binutils-gdb] Move TUI testcases to new gdb/testsuite/gdb.tui/ directory sergiodj+buildbot
2017-03-08 19:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-08  2:52 [binutils-gdb] Fix PR tui/21216: TUI line breaks regression sergiodj+buildbot
2017-03-09  3:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-08 13:45 [binutils-gdb] "gdb.arch/i386-pkru.exp: probe PKRU support" shouldn't FAIL if not supported sergiodj+buildbot
2017-03-09 15:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-08 20:33 [binutils-gdb] Add support for the new 'lnia' extended mnemonic sergiodj+buildbot
2017-03-11 12:47 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-08 22:52 [binutils-gdb] Avoid unstable test message in gdb.base/step-over-exit.exp sergiodj+buildbot
2017-03-12  9:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-09  3:06 [binutils-gdb] Update -maltivec and -mvsx options to only enable their oldest instructions sergiodj+buildbot
2017-03-13  5:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-09 16:05 [binutils-gdb] Use CpuCET on rdsspq sergiodj+buildbot
2017-03-14  1:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-09 16:53 [binutils-gdb] Fix compile time warnings about using possibly uninitialised variables in rs6000-core.c sergiodj+buildbot
2017-03-15 13:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-13 10:26 [binutils-gdb] Rename R_AARCH64_TLSDESC_LD64_LO12_NC to R_AARCH64_TLSDESC_LD64_LO12 and R_AARCH64_TLSDESC_ADD_LO12_NC to R_AARCH64_TLSDESC_ADD_LO12 sergiodj+buildbot
2017-03-24  8:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22  1:38 [binutils-gdb] gdbserver: Use pattern rule for objects from common/ sergiodj+buildbot
2017-03-31  6:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22  2:06 [binutils-gdb] Introduce regcache_get_ptid sergiodj+buildbot
2017-04-05 11:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22  2:36 [binutils-gdb] amd64-linux-nat: Use ptid from regcache instead of inferior_ptid sergiodj+buildbot
2017-04-07  4:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22  3:39 [binutils-gdb] aix-thread: Use ptid from regcache instead of inferior_ptid sergiodj+buildbot
2017-04-08 22:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22  7:47 [binutils-gdb] Fix expect for gdb.cp/m-static.exp sergiodj+buildbot
2017-04-18  9:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22 12:43 [binutils-gdb] E6500 spr mnemonics sergiodj+buildbot
2017-04-28  6:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22 13:04 [binutils-gdb] Fix PR gdb/19637: bound_registers.py: Add support for Python 3 sergiodj+buildbot
2017-04-29 15:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22 17:59 [binutils-gdb] hppa-obsd-nat: Use ptid from regcache instead of inferior_ptid sergiodj+buildbot
2017-05-06 20:51 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22 19:22 [binutils-gdb] i386-gnu-nat: Use ptid from regcache instead of inferior_ptid sergiodj+buildbot
2017-05-09 10:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22 20:08 [binutils-gdb] Add DW_OP_GNU_variable_value sergiodj+buildbot
2017-04-15 19:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-22 23:28 [binutils-gdb] Add ability to return rvalue reference values from value_ref sergiodj+buildbot
2017-05-18  6:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-23  0:29 [binutils-gdb] Support DW_TAG_rvalue_reference type sergiodj+buildbot
2017-05-21 22:05 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-23  1:42 [binutils-gdb] Add rvalue references to overloading resolution sergiodj+buildbot
2017-05-24 17:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-23 15:04 [binutils-gdb] Remove AARCH64_RECORD_FAILURE sergiodj+buildbot
2017-06-07 15:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-23 16:19 [binutils-gdb] Remove MAX_REGISTER_SIZE from sol-thread.c sergiodj+buildbot
2017-06-10 11:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-24  7:12 [binutils-gdb] Change {lookup,make}_reference_type API sergiodj+buildbot
2017-05-17  9:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-24 15:38 [binutils-gdb] Avoid segfault on invalid directory table sergiodj+buildbot
2017-06-12  6:15 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-24 16:24 [binutils-gdb] Add rvalue reference tests and docs sergiodj+buildbot
2017-05-25 13:46 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-24 21:27 [binutils-gdb] arc/nps400: Add cp16/cp32 instructions to opcodes library sergiodj+buildbot
2017-05-29 22:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-25 10:49 [binutils-gdb] Remove some unnecessary inferior_ptid setting/restoring when fetching/storing registers sergiodj+buildbot
2017-06-11  8:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-27 11:49 [binutils-gdb] Add minimal support for WebAssembly backend to the BFD library sergiodj+buildbot
2017-06-16  1:38 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-27 11:50 [binutils-gdb] PR21303, objdump doesn't show e200z4 insns sergiodj+buildbot
2017-06-17 18:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-27 15:29 [binutils-gdb] gdb/cp-name-parser.y: Eliminate make_empty, use cplus_demangle_fill_component sergiodj+buildbot
2017-06-21 21:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-27 21:13 [binutils-gdb] gdbserver: xtensa: add call0 support sergiodj+buildbot
2017-06-26  9:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-27 22:23 [binutils-gdb] gdbserver: xtensa: support THREADPTR register sergiodj+buildbot
2017-06-28 14:50 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-28 18:58 [binutils-gdb] arc: Align internal regnums with architectural regnums sergiodj+buildbot
2017-06-29 11:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-03-28 20:37 [binutils-gdb] arc: Add prologue analysis sergiodj+buildbot
2017-07-01 22:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-03 16:30 [binutils-gdb] IA16 support sergiodj+buildbot
2017-07-15 19:28 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-04 10:51 [binutils-gdb] Fix null pointer dereferences when using a link built with clang sergiodj+buildbot
2017-07-17 19:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-04 14:49 [binutils-gdb] remote.c: Use ptid_t instead of struct ptid sergiodj+buildbot
2017-07-18 16:23 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-04 20:48 [binutils-gdb] dwarf2read.c: Make dir_index and file_name_index strong typedefs sergiodj+buildbot
2017-07-24 16:09 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-04 21:06 [binutils-gdb] Make sect_offset and cu_offset strong typedefs instead of structs sergiodj+buildbot
2017-07-25 13:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-04 23:00 [binutils-gdb] Remove support for FreeBSD/alpha sergiodj+buildbot
2017-07-28  1:04 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-05  1:01 [binutils-gdb] Initialize gdb::optional empty payload to quiet false -Wmaybe-uninitialized warnings sergiodj+buildbot
2017-07-29 17:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-05 14:11 [binutils-gdb] Fix racy test in gdb.threads/thread-specific-bp.exp sergiodj+buildbot
2017-08-01  8:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-05 15:20 [binutils-gdb] Use frame_unwind_register_value in frame_unwind_register_unsigned sergiodj+buildbot
2017-08-02  4:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-05 20:34 [binutils-gdb] -Wwrite-strings: Constify shell_escape and plug make_command leak sergiodj+buildbot
2017-08-07  7:27 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-05 21:07 [binutils-gdb] -Wwrite-strings: Don't initialize string command variables to empty string sergiodj+buildbot
2017-08-06 10:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-06  0:12 [binutils-gdb] -Wwrite-strings: More fix-old-Python-API wrappers sergiodj+buildbot
2017-08-14  6:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-06  1:31 [binutils-gdb] -Wwrite-strings: execute_command calls with string literals sergiodj+buildbot
2017-08-17  6:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-06  4:14 [binutils-gdb] ptid_{lwp,tid}_p: Remove unnecessary checks sergiodj+buildbot
2017-08-22 19:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-06 12:43 [binutils-gdb] -Wwrite-strings: More Solaris sergiodj+buildbot
2017-08-20 12:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-04-06 16:16 [binutils-gdb] Regen SRC-POTFILES.in sergiodj+buildbot
2017-08-23 17:36 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-24 21:53 [binutils-gdb] Remove unused function set_inferior_target_data sergiodj+buildbot
2017-09-01  4:41 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-25  9:18 [binutils-gdb] gdbserver: Rename some functions, thread -> inferior sergiodj+buildbot
2017-09-02  2:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-26  0:39 [binutils-gdb] x86: Remove redundant "symbol" in comments sergiodj+buildbot
2017-09-02 22:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <74081948353b117fcbe870fc3cc9ebe0f18fdcf8@gdb-build>
2017-08-26 11:48 ` sergiodj+buildbot
2017-08-26 11:54 [binutils-gdb] PowerPC TPREL reloc handling sergiodj+buildbot
2017-09-04 16:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
     [not found] <f1902523c9b7941775a2c64af89de0f111b8924c@gdb-build>
2017-08-27  2:46 ` sergiodj+buildbot
2017-08-27 14:46 [binutils-gdb] x86: Initialize def_protected sergiodj+buildbot
2017-09-06  6:06 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-28 18:53 [binutils-gdb] x86: Check for valid PLT section size sergiodj+buildbot
2017-09-07  7:44 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-28 23:21 [binutils-gdb] Remove unused _bfd_elf_ifunc_get_synthetic_symtab sergiodj+buildbot
2017-09-10 16:59 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-29 13:35 [binutils-gdb] Fix simulation of MSP430's open system call sergiodj+buildbot
2017-09-11 21:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-29 18:16 [binutils-gdb] x86: Check valid PLT sections before checking dynamic relocations sergiodj+buildbot
2017-09-12 19:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-29 18:56 [binutils-gdb] x86: Simplify bad return in get_synthetic_symtab sergiodj+buildbot
2017-09-14  1:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-29 22:11 [binutils-gdb] x86: Re-indent elf32-i386.c/elf64-x86-64.c sergiodj+buildbot
2017-09-15 12:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-30 11:36 [binutils-gdb] PowerPC64 __tls_get_addr sequence optimization sergiodj+buildbot
2017-09-17 23:49 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-30 12:05 [binutils-gdb] PowerPC TPREL16_HA/LO reloc optimization sergiodj+buildbot
2017-09-18 11:30 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-30 12:51 [binutils-gdb] Remove elf_x86_64_next_tls_desc_index/elf_x86_64_srelplt2 sergiodj+buildbot
2017-09-19  7:03 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-30 15:38 [binutils-gdb] MIPS/BFD: Correct microMIPS cross-mode BAL to JALX relaxation sergiodj+buildbot
2017-09-20 23:56 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-30 16:30 [binutils-gdb] x86: Add _bfd_x86_elf_link_hash_table_create sergiodj+buildbot
2017-09-21 19:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-30 19:49 [binutils-gdb] x86: Add _bfd_x86_elf_get_synthetic_symtab sergiodj+buildbot
2017-09-23 17:11 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-31  1:26 [binutils-gdb] bfd_close_all_done calling _close_and_cleanup sergiodj+buildbot
2017-09-24  9:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-31  3:19 [binutils-gdb] FT32: Permit R_FT32_18 overflow sergiodj+buildbot
2017-09-25  6:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-31  4:05 [binutils-gdb] Add elf64.lo together with elfxx-x86.lo for 64-bit BFD sergiodj+buildbot
2017-09-27  4:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-31  4:27 [binutils-gdb] PR22048, Incorrect .eh_frame section in libc.so sergiodj+buildbot
2017-09-27 23:32 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-31 16:43 [binutils-gdb] Fix buffer read overrun by ensuring that DWARF sections containing strings always end in a NUL byte sergiodj+buildbot
2017-10-02 13:00 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-08-31 22:00 [binutils-gdb] Implement the ability to set/unset environment variables to GDBserver when starting the inferior sergiodj+buildbot
2017-10-03 10:14 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-09-01  5:02 [binutils-gdb] PR gdb/22046: Fix T-stopped detach regression on old Linux kernels sergiodj+buildbot
2017-10-04  6:39 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-04 16:48 [binutils-gdb] Fix -list-thread-groups --available logic and add test sergiodj+buildbot
2017-10-04 23:57 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-04 17:39 [binutils-gdb] Redesign mock environment for gdbarch selftests sergiodj+buildbot
2017-10-05 19:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-04 17:39 [binutils-gdb] Fix "Remote 'g' packet reply is too long" problems with multiple inferiors sergiodj+buildbot
2017-10-11 11:43 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-04 23:08 [binutils-gdb] PR21167, relocation sections not included in groups sergiodj+buildbot
2017-10-12  8:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05  1:09 [binutils-gdb] bfd_error_on_input is for archives sergiodj+buildbot
2017-10-13 15:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05  1:42 [binutils-gdb] bfd_set_input_error sergiodj+buildbot
2017-10-14 12:26 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05  4:45 [binutils-gdb] Update my email address sergiodj+buildbot
2017-10-15  8:33 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05 13:02 [binutils-gdb] tile: Dump dynamic relocation info to the map file sergiodj+buildbot
2017-10-16  9:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05 17:00 [binutils-gdb] Handle the NT_ARM_VFP core dump note on FreeBSD sergiodj+buildbot
2017-10-18  3:55 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05 17:00 [binutils-gdb] Add a signal frame unwinder for FreeBSD/mipsn32 sergiodj+buildbot
2017-10-19  2:52 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05 17:00 [binutils-gdb] Handle FreeBSD-specific AT_EHDRFLAGS and AT_HWCAP auxiliary vector types sergiodj+buildbot
2017-10-17  6:10 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05 17:18 [binutils-gdb] Remove unused "union agent_val" from ax.h sergiodj+buildbot
2017-10-21 20:58 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05 17:18 [binutils-gdb] Clean up some DFP interfaces sergiodj+buildbot
2017-10-20 21:21 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05 17:18 [binutils-gdb] Clean up includes of doublest.h and floatformat.h sergiodj+buildbot
2017-10-20  0:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-05 17:35 [binutils-gdb] Fix fork-related regressions on GNU/Linux sergiodj+buildbot
2017-10-22 17:40 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06  7:18 [binutils-gdb] x86: Add TLS_TRANSITION_IE_TO_LE_P sergiodj+buildbot
2017-10-24  9:37 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06  7:26 [binutils-gdb] x86: Add NEED_DYNAMIC_RELOCATION_P sergiodj+buildbot
2017-10-25  5:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06  7:30 [binutils-gdb] Add RESOLVED_LOCALLY_P sergiodj+buildbot
2017-10-26  1:08 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06  7:36 [binutils-gdb] x86: Add GENERATE_RELATIVE_RELOC_P sergiodj+buildbot
2017-10-26 22:01 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06  7:49 [binutils-gdb] x86: Add COPY_INPUT_RELOC_P sergiodj+buildbot
2017-10-29 11:25 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06  9:53 [binutils-gdb] gdb: Fix decoding of ARM neon memory hint insns sergiodj+buildbot
2017-11-01  1:31 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06 10:17 [binutils-gdb] [RFC] Replicate src dir in build dir sergiodj+buildbot
2017-11-01 23:20 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06 10:23 [binutils-gdb] Share code updating gdb_target_obs sergiodj+buildbot
2017-11-02 19:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06 11:06 [binutils-gdb] Fix more GDB build breakage on mingw32 sergiodj+buildbot
2017-11-06  1:45 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06 12:54 [binutils-gdb] Add "do/while(0); " to COPY_INPUT_RELOC_P/VERIFY_COPY_RELOC sergiodj+buildbot
2017-11-06 21:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06 13:38 [binutils-gdb] Move arm.o arm-get-next-pcs.o arm-linux.o to arch/ sergiodj+buildbot
2017-11-08 17:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06 21:43 [binutils-gdb] Account for padding in FreeBSD/mipsn32 NT_PRSTATUS notes sergiodj+buildbot
2017-11-10  9:42 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-06 22:49 [binutils-gdb] Skip gdb.mi/mi-threads-interrupt.exp if nointerrupts sergiodj+buildbot
2017-11-11  5:53 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-07  0:08 [binutils-gdb] x86: Update UNDEFINED_WEAK_RESOLVED_TO_ZERO comments sergiodj+buildbot
2017-11-12 23:16 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-07  1:04 [binutils-gdb] x86: Use zero_undefweak in elf_x86_link_hash_entry sergiodj+buildbot
2017-11-12  2:35 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-09  5:11 [binutils-gdb] PR22212, memory leak in nm sergiodj+buildbot
2017-11-19  7:13 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-09 12:16 [binutils-gdb] Fix gdb.base/print-file-var-main.c value check logic sergiodj+buildbot
2017-11-24  8:54 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-09 17:56 [binutils-gdb] S/390: Sync with latest POP - 3 new instructions sergiodj+buildbot
2017-11-29 10:29 ` Failures on Fedora-ppc64le-m64, branch master sergiodj+buildbot
2017-10-09 18:14 [binutils-gdb] Don't try building gdb against guile-2.2 sergiodj+buildbot
2017-12-02  3:15 ` Failures on Fedora-ppc64le-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).