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] Remove some usages of get_dwarf2_per_objfile
Date: Sat, 07 Apr 2018 19:29:00 -0000	[thread overview]
Message-ID: <12359b5e8f2a4034e1e4cd7f0b454fb03151df4c@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 12359b5e8f2a4034e1e4cd7f0b454fb03151df4c ***

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

Remove some usages of get_dwarf2_per_objfile

This patch removes some usages of get_dwarf2_per_objfile, where we can
get hold of the dwarf2_per_objfile object in a simpler way.  For
example, it's simpler (and slightly less work) to pass
dwarf2_per_objfile and get the objfile from it than to pass the objfile
and call get_dwarf2_per_objfile.

Ideally, get_dwarf2_per_objfile should only be used in the entry points
of the dwarf2 code, where we receive an objfile.

gdb/ChangeLog:

	* dwarf2read.c (create_cus_from_index_list): Replace objfile arg
	with dwarf2_per_objfile.
	(create_cus_from_index): Likewise.
	(create_signatured_type_table_from_index): Likewise.
	(dwarf2_read_index): Likewise.
	(dwarf2_initialize_objfile): Likewise.
	(dwarf2_fetch_die_loc_sect_off):  Get dwarf2_per_objfile from
	per_cu rather than get_dwarf2_per_objfile.


             reply	other threads:[~2018-04-07 19:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07 19:29 sergiodj+buildbot [this message]
2018-04-07 19:29 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-04-08  1:13 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-04-08  1:19 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-04-08  1:31 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-04-08  1:40 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-04-08  1:47 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-04-08  1:50 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-04-08  2:37 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-04-08  4:26 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-04-08  4:52 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-04-08  5:18 ` Failures on Ubuntu-AArch32-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=12359b5e8f2a4034e1e4cd7f0b454fb03151df4c@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).