This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Export stack_used as __stack_used
- From: Andreas Schwab <schwab at linux-m68k dot org>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: Pedro Alves <palves at redhat dot com>, Gary Benson <gbenson at redhat dot com>, libc-alpha at sourceware dot org
- Date: Mon, 20 Jun 2016 11:04:38 +0200
- Subject: Re: [PATCH] Export stack_used as __stack_used
- Authentication-results: sourceware.org; auth=none
- References: <20160613112351 dot GA655 at blade dot nx> <1466163476-10459-1-git-send-email-gbenson at redhat dot com> <f6867d8f-3532-1ac2-cc7f-e7bb6ea12202 at redhat dot com> <20160617195018 dot GA20374 at blade dot nx> <ce9c88a4-5709-707e-c598-d438198df85f at redhat dot com> <987ac43c-9883-a194-9860-58e13cbe54e9 at redhat dot com> <m2bn2zyoo7 dot fsf at linux-m68k dot org> <6809739e-ef4f-fd2f-7b8f-5cab5d52bf95 at redhat dot com> <db7fd0cc-287c-f08d-9de7-b00bdac0993a at redhat dot com>
Florian Weimer <fweimer@redhat.com> writes:
> Could we export a single symbol which is a struct and contains all the
> data we need? Then the impact on dynamic symbol table size would be
> minimal.
That would raise the issue of compatibility. Probing each symbol
separately is much easier than trying to extend the struct. What
exactly _is_ the impact of making the dynamic symtab a few entries
bigger?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."