From: Alan Modra <amodra@gmail.com>
To: Fangrui Song <i@maskray.me>
Cc: Haim Shimonovich <Haim.Shimonovich@ceva-dsp.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: objdump very long run time when using -D -z flags
Date: Fri, 1 May 2020 13:52:05 +0930 [thread overview]
Message-ID: <20200501042205.GC25855@bubble.grove.modra.org> (raw)
In-Reply-To: <BN7PR15MB22741FE56EAB113951280EFFCBAB0@BN7PR15MB2274.namprd15.prod.outlook.com>
On Thu, Apr 30, 2020 at 06:22:11PM -0700, Fangrui Song wrote:
> This just hides the problem.
That isn't true.
> -z is still going to be slow.
Well, yes, because objdump is going to be showing many instructions.
> To avoid
> the quadratic behavior, we should increase the address by at least `z`
> if we have scanned `z` zeros.
What quadratic behaviour related to blocks of zeros? With -z we now
won't scan, and without -z the entire block (or almost) is consumed.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2020-05-01 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 14:26 Haim Shimonovich
2020-05-01 1:22 ` Fangrui Song
2020-05-01 4:22 ` Alan Modra [this message]
2020-05-01 4:13 ` Alan Modra
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=20200501042205.GC25855@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=Haim.Shimonovich@ceva-dsp.com \
--cc=binutils@sourceware.org \
--cc=i@maskray.me \
/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).