This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Performance issues with -ffunction-sections and dwarf2 debug line info


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.

Here is the patch I would like to submit to the head and if it is still possible to the binutils 2.17 branch.

Thanks in advance for your comments

Nicolas

Index: dwarf2dbg.c
===================================================================
RCS file: /cvs/src/src/gas/dwarf2dbg.c,v
retrieving revision 1.81
diff -r1.81 dwarf2dbg.c
128c128,131
< static struct line_seg *all_segs;
---
> static struct line_seg *all_segs = NULL;
>
> /* Pointer to the last item in all_segs. NULL if all_segs is empty */
> static struct line_seg *all_segs_last = NULL;
223c226
< s->next = all_segs;
---
> s->next = NULL;
226c229,245
< all_segs = s;
---
>
> /* Append s at the end of the all_segs list. Appending it to the head is
> not recommended as this will break the line debug info order (when
> compiling using -ffunction-sections). Ensuring that line appears in order
> with increasing VMAs helps reading that info afterward from a
> performance point of view (see comments in add_line_info (bfd/dwarf2.c).
> */
> if (all_segs_last)
> {
> all_segs_last->next = s;
> all_segs_last = s;
> }
> else
> {
> all_segs = s;
> all_segs_last = s;
> }



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]