This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch users/hjl/check_relocs in repository binutils-gdb.
discards bc3799c772 ELF: Call check_relocs after opening all inputs adds 0c478e2d06 Remove "do_nothing" adds 1a56bfa56e Remove free_splay_tree cleanup adds f8f762b2fd Automatic date update in version.in adds cbd3b1c155 Correct ld/Makefile earmelfb_fuchsia dependencies adds b9399fcf4e Prepare powerpc64 for late check_relocs adds fc3c534364 riscv: Cache the max alignment of output sections new 7ba06b0ec8 ELF: Call check_relocs after opening all inputs
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (bc3799c772) \ N -- N -- N refs/heads/users/hjl/check_relocs (7ba06b0ec8)
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: bfd/ChangeLog | 20 ++++ bfd/elf64-ppc.c | 138 +++++++++++++---------- bfd/elfnn-riscv.c | 16 ++- bfd/version.h | 2 +- gdb/ChangeLog | 11 ++ gdb/{selftest-arch.h => common/gdb_splay_tree.h} | 31 +++-- gdb/mi/mi-main.c | 29 ++--- ld/ChangeLog | 5 + ld/Makefile.am | 2 +- ld/Makefile.in | 2 +- 10 files changed, 162 insertions(+), 94 deletions(-) copy gdb/{selftest-arch.h => common/gdb_splay_tree.h} (63%)