From: Nicolas Roche <roche@adacore.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: binutils@sources.redhat.com
Subject: Re: Performance issues with -ffunction-sections and dwarf2 debug line info
Date: Fri, 28 Apr 2006 13:10:00 -0000 [thread overview]
Message-ID: <4451F067.4090401@adacore.com> (raw)
In-Reply-To: <20060428040629.GA11666@bubble.grove.modra.org>
Alan Modra wrote:
>
> Thanks for the analysis and patch. It looks OK to me as all places that
> traverse the list don't care too much about the order. I'm going to
> apply the following slightly different patch instead, so we don't need
> another static var and to make line_seg and line_subseg list addition
> look similar.
Thanks for your review (I just see that I forgot to provide a Changelog
entry ... will do next time).
Just a little question. Will you apply that patch on the 2.17 branch as
well so that this fix is included in the upcoming 2.17 release ?
Nicolas Roche
next prev parent reply other threads:[~2006-04-28 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 14:38 Nicolas Roche
2006-04-28 12:23 ` Alan Modra
2006-04-28 13:10 ` Nicolas Roche [this message]
2006-04-28 18:15 ` Alan Modra
2006-05-01 21:33 ` Nicolas Roche
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=4451F067.4090401@adacore.com \
--to=roche@adacore.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.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).