public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Tom Tromey <tromey@adacore.com>,
	 Ulrich Weigand <ulrich.weigand@de.ibm.com>,
	 Andreas Arnez <arnez@linux.ibm.com>,
	binutils@sourceware.org
Subject: Re: [PATCH] gdb: do not add const sections to the section map
Date: Thu, 19 May 2022 09:10:03 -0600	[thread overview]
Message-ID: <875ym1d0dw.fsf@tromey.com> (raw)
In-Reply-To: <20220516194209.2470009-1-iii@linux.ibm.com> (Ilya Leoshkevich's message of "Mon, 16 May 2022 21:42:09 +0200")

>>>>> Ilya Leoshkevich <iii@linux.ibm.com> writes:

> From: Ulrich Weigand <ulrich.weigand@de.ibm.com>
> build_objfile_section_table () creates four synthetic sections, which
> significantly slow down section map sorting.  This is especially
> noticeable when debugging JITs that report a lot of objfiles.  Since
> these sections are not useful for find_pc_section (), do not add them
> to the section map.

How does it slow down the sorting?

It seems a little strange at least to drop the *ABS* section, since IIUC
that's for symbols that specify some kind of absolute address.  Couldn't
these matter for lookup purposes?  It's probable I don't really know
what's going on here...

I wonder if we can drop all support for all these sections from gdb.

Tom

  parent reply	other threads:[~2022-05-19 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 19:42 Ilya Leoshkevich
2022-05-17 14:52 ` Andrew Burgess
2022-05-19 15:10 ` Tom Tromey [this message]
2022-05-19 17:37   ` Ilya Leoshkevich

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=875ym1d0dw.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=arnez@linux.ibm.com \
    --cc=binutils@sourceware.org \
    --cc=iii@linux.ibm.com \
    --cc=ulrich.weigand@de.ibm.com \
    /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).