From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Alan Hayward <alan.hayward@arm.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] LONGEST and ULONGEST function template instantiation
Date: Thu, 15 Jun 2017 16:19:00 -0000 [thread overview]
Message-ID: <d8b11d42-54ab-96da-786a-f535fb057077@redhat.com> (raw)
In-Reply-To: <8660fxv4vi.fsf@gmail.com>
On 06/15/2017 12:59 PM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
>
> Hi Pedro,
> I pick up your patch, and update the ChangeLog entry.
Thanks. FAOD, fine with me to push it in.
>> The version below has no impact on code size:
>>
>> $ size gdb.before gdb.after
>> text data bss dec hex filename
>> 7535236 125008 181184 7841428 77a694 gdb.before
>> 7535236 125008 181184 7841428 77a694 gdb.after
>
> I can't reproduce your result with gcc 5.4.0 on Ubuntu 16.04. The
> patched GDB size increased by 112, but it doesn't matter.
>
> before:
> $ size ./gdb
> text data bss dec hex filename
> 7733505 144208 180768 8058481 7af671 ./gdb
>
> after:
> $ size ./gdb
> text data bss dec hex filename
> 7733617 144208 180768 8058593 7af6e1 ./gdb
Curious, I see the same too now. Dunno what I did
before.
Diffing "size -A" (and stripping addr column) shows:
-gdb.before.stripped :
+gdb.after.stripped :
.rela.plt 16344
.init 26
.plt 10912
-.text 4239945
+.text 4239705
.fini 9
-.rodata 2280312
+.rodata 2280728
.stapsdt.base 1
-.eh_frame_hdr 126004
-.eh_frame 745124
+.eh_frame_hdr 125996
+.eh_frame 745084
So it results in less code after all. The increase is
in .rodata. Maybe the result of longer mangled names or
longer strings for __FUNCTION__.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-06-15 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 11:29 Yao Qi
2017-06-13 11:33 ` Yao Qi
2017-06-14 13:54 ` Alan Hayward
2017-06-14 16:12 ` Pedro Alves
2017-06-15 11:59 ` Yao Qi
2017-06-15 16:19 ` Pedro Alves [this message]
2017-06-16 14:46 ` Yao Qi
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=d8b11d42-54ab-96da-786a-f535fb057077@redhat.com \
--to=palves@redhat.com \
--cc=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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).