From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18102 invoked by alias); 15 Jan 2013 10:10:34 -0000 Received: (qmail 18083 invoked by uid 22791); 15 Jan 2013 10:10:33 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_BP,TW_GD,TW_YP X-Spam-Check-By: sourceware.org Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 Jan 2013 10:10:27 +0000 Received: by mail-vc0-f173.google.com with SMTP id fl15so390624vcb.32 for ; Tue, 15 Jan 2013 02:10:27 -0800 (PST) Received: by 10.58.23.169 with SMTP id n9mr106125641vef.58.1358244626968; Tue, 15 Jan 2013 02:10:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.215.38 with HTTP; Tue, 15 Jan 2013 02:09:46 -0800 (PST) From: Steven Bosscher Date: Tue, 15 Jan 2013 10:10:00 -0000 Message-ID: Subject: stabs/dwarf size comparison on CSiBE (Was: stabs support in binutils, gcc, and gdb) To: binutils@sourceware.org Cc: Andreas Schwab , David Taylor , Doug Evans , nick clifton , gcc@gcc.gnu.org, gdb Content-Type: text/plain; charset=ISO-8859-1 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2013-01/txt/msg00059.txt.bz2 Hello, In this stabs vs. dwarf discussion, so far it's more been about assumptions than numbers. So let's throw in some numbers! The following debug sizes are for CSiBE-v2.1.1 on mipsisa64-elf, with the LRA branch at r195108. All CSiBE test cases are packages written in C. Debug size is computed as the total size of all ".stabs*" or ".debug*" sections as computed by "size -A" (sysv style size output) on individual object files (so before linking) and summed up by awk (*). Tested debug formats are "none", "stabs", "dwarf2", and "dwarf4". Compiler options were "-Os" for all four tested debug formats. Debug info was output with "-gstabs", "-gdwarf-2", and "-gdwarf-4". And the results are: package stabs dwarf2 dwarf4 bzip2-1.0.2 372772 289386 279670 cg_compiler... 1355948 1381734 1314676 compiler 152178 156644 148458 flex-2.5.31 665588 511856 488256 jikespg-1.3 944126 773358 749050 jpeg-6b 3285854 2186640 2110290 libmspack 602692 421792 407070 libpng-1.2.5 1064722 1017116 975098 linux-2.4.23... 53617230 40921246 38353402 lwip-0.5.3... 576260 402830 381902 mpeg2dec-0.3.1 492918 336912 327072 mpgcut-1.1 46956 51854 49490 OpenTCP-1.0.4 873008 223646 212822 replaypc-0.4... 1009322 445296 424136 teem-1.6.0-src 13374436 7259308 6954802 ttt-0.10.1... 208516 113828 109776 unrarlib-0.4.0 91236 79396 75256 zlib-1.1.4 280272 201392 193506 TOTAL 79014034 56774234 53554732 DEBUG/TEXT 16.49 11.85 11.18 (*) the test script actually takes the sum of sizes for all ".text*", ".stabs*", and ".debug*" sections, and the ".text*" size is subtracted to get the debug info sizes. Unless someone can shoot holes in this test approach, the results suggest that DWARF debug size is *smaller* than stabs, at least for mipsisa64. Ciao! Steven