From c766f7ecdd6fae075bf21508770bbc296faf4d60 Mon Sep 17 00:00:00 2001 From: Doug Evans Date: Mon, 10 Dec 2012 21:06:00 +0000 Subject: [PATCH] * dwarf2read.c (create_dwo_in_dwp): Tweak comment. --- gdb/ChangeLog | 2 ++ gdb/dwarf2read.c | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index cbc3e7cbfdd..5f9ef4db5ed 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,7 @@ 2012-12-10 Doug Evans + * dwarf2read.c (create_dwo_in_dwp): Tweak comment. + * symtab.c (find_pc_sect_symtab): Add comment. 2012-12-10 Tom Tromey diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c index 2168c69ef2d..7a1bbc5bf7a 100644 --- a/gdb/dwarf2read.c +++ b/gdb/dwarf2read.c @@ -8594,8 +8594,8 @@ create_dwo_in_dwp (struct dwp_file *dwp_file, have dwo_unit "live" in that. At least for now. The DWP file can be made up of a random collection of CUs and TUs. - However, for each CU + set of TUs that came from the same original - DWO file, we want combine them back into a virtual DWO file to save space + However, for each CU + set of TUs that came from the same original DWO + file, we want to combine them back into a virtual DWO file to save space (fewer struct dwo_file objects to allocated). Remember that for really large apps there can be on the order of 8K CUs and 200K TUs, or more. */ -- 2.30.2