public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] x86-64: Don't pass output_bfd to info->callbacks->minfo
Date: Tue, 26 Sep 2017 22:02:00 -0000	[thread overview]
Message-ID: <ac69a0d75bf472a140e5405c8a90420d5f63a998@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT ac69a0d75bf472a140e5405c8a90420d5f63a998 ***

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

x86-64: Don't pass output_bfd to info->callbacks->minfo

Don't pass output_bfd to info->callbacks->minfo when dumping local IFUNC
functions in the map file.

	PR ld/22199
	* elf64-x86-64.c (elf_x86_64_finish_dynamic_symbol): Don't pass
	output_bfd to info->callbacks->minfo.


             reply	other threads:[~2017-09-26 22:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26 22:02 sergiodj+buildbot [this message]
2017-09-26 22:09 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2017-09-26 22:13 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-09-26 22:20 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-09-26 22:23 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-09-26 22:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-09-26 22:56 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-09-26 23:43 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-09-27  0:32 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-09-27  2:44 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-09-27  6:19 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-09-27  6:30 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-09-27  6:36 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ac69a0d75bf472a140e5405c8a90420d5f63a998@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).