From: Alan Modra <amodra@gmail.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: [PR24444] speed up locview resolution wiht relaxable frags
Date: Fri, 03 May 2019 01:14:00 -0000 [thread overview]
Message-ID: <20190503011420.GG3195@bubble.grove.modra.org> (raw)
In-Reply-To: <or1s1kdoul.fsf@lxoliva.fsfla.org>
On Tue, Apr 30, 2019 at 02:49:38AM -0300, Alexandre Oliva wrote:
> AFAICT fixing this will require introducing artificial undefined symbols
> to be used as previous view label and previous view number for each
> subsection, and then, when ordering subsections and sections, defining
> the initial previous symbols of each subsection as equal to the final
> previous symbols of the previous subsection in the same section.
Don't you already keep struct line_entry on per-subseg lists? Frags
too are kept on per-subseg lists until chain_frchains_together.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2019-05-03 1:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 8:57 Alexandre Oliva
2019-04-14 13:22 ` Alan Modra
2019-04-16 13:24 ` Alexandre Oliva
2019-04-17 1:32 ` Alan Modra
2019-04-24 23:18 ` Alan Modra
2019-04-30 5:49 ` Alexandre Oliva
2019-05-03 1:14 ` Alan Modra [this message]
2019-05-04 0:56 ` Alexandre Oliva
2019-05-04 3:22 ` Alexandre Oliva
2019-05-04 5:44 ` 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=20190503011420.GG3195@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=aoliva@redhat.com \
--cc=binutils@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).