public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: Nicolas Roche <roche@adacore.com>
Cc: binutils@sources.redhat.com
Subject: Re: Performance issues with -ffunction-sections and dwarf2 debug line  info
Date: Fri, 28 Apr 2006 12:23:00 -0000	[thread overview]
Message-ID: <20060428040629.GA11666@bubble.grove.modra.org> (raw)
In-Reply-To: <444F4B7E.7080806@adacore.com>

On Wed, Apr 26, 2006 at 12:29:18PM +0200, Nicolas Roche wrote:
> I am using GCC 3.4 and the -ffunction-sections -fdata-sections options 
> along with binutils 2.16.1 (for dead code elimination)
> 
> When using this functions the debug line info is no more sorted 
> (increasing line and increasing vma) and so on big files with lots of 
> functions you can observe a quadratic behavior for the time needed to 
> read this info (addr2line, ...). The reason is that we are almost always 
> triggering the worst case in add_line_info function in bfd/dwarf2.c.
> 
> The problem is in gas. Indeed in dwarf2dbg.c a list of sections is 
> maintained (all_segs), but each time a new section is created, it is 
> appended to the beginning of the list....
> 
> so if  you have the following source:
> 
> 1 begin function1
> 2
> 3 end function1
> 4 begin function2
> 5
> 6 end function2
> 
> the line information will be sorted in the following order:
> 4,5,6,1,2,3
> 
> In order to solve this issue we just have to append to the tail of all_segs.

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.

	* dwarf2dbg.c (get_line_subseg): Attach new struct line_seg to end
	of list rather than beginning.

Index: gas/dwarf2dbg.c
===================================================================
RCS file: /cvs/src/src/gas/dwarf2dbg.c,v
retrieving revision 1.81
diff -u -p -r1.81 dwarf2dbg.c
--- gas/dwarf2dbg.c	28 Feb 2006 00:38:19 -0000	1.81
+++ gas/dwarf2dbg.c	27 Apr 2006 03:18:54 -0000
@@ -209,21 +209,21 @@ get_line_subseg (segT seg, subsegT subse
   static subsegT last_subseg;
   static struct line_subseg *last_line_subseg;
 
-  struct line_seg *s;
+  struct line_seg **ps, *s;
   struct line_subseg **pss, *ss;
 
   if (seg == last_seg && subseg == last_subseg)
     return last_line_subseg;
 
-  for (s = all_segs; s; s = s->next)
+  for (ps = &all_segs; (s = *ps) != NULL; ps = &s->next)
     if (s->seg == seg)
       goto found_seg;
 
   s = (struct line_seg *) xmalloc (sizeof (*s));
-  s->next = all_segs;
+  s->next = NULL;
   s->seg = seg;
   s->head = NULL;
-  all_segs = s;
+  *ps = s;
 
  found_seg:
   for (pss = &s->head; (ss = *pss) != NULL ; pss = &ss->next)

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

  reply	other threads:[~2006-04-28  4:06 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 [this message]
2006-04-28 13:10   ` Nicolas Roche
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=20060428040629.GA11666@bubble.grove.modra.org \
    --to=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=roche@adacore.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).