From: Florian Weimer <fweimer@redhat.com>
To: Vineet Gupta via Libc-alpha <libc-alpha@sourceware.org>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
arcml <linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH v2] elf: Change TLS static surplus default back to 1664
Date: Mon, 20 Jul 2020 16:33:53 +0200 [thread overview]
Message-ID: <878sfew90u.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <95bfdf25-19b3-33b6-15a0-f4ba4326bf11@synopsys.com> (Vineet Gupta via Libc-alpha's message of "Sun, 19 Jul 2020 04:39:37 +0000")
* Vineet Gupta via Libc-alpha:
> Hi Florian,
>
> On 7/17/20 4:41 AM, Florian Weimer via Libc-alpha wrote:
>> Make the computation in elf/dl-tls.c more transparent, and add
>> an explicit test for the historic value.
>>
>> ---
>> elf/Makefile | 4 +++-
>> elf/dl-tls.c | 37 ++++++++++++++++++++++++++++++-------
>> elf/tst-tls-surplus.c | 42 ++++++++++++++++++++++++++++++++++++++++++
>> 3 files changed, 75 insertions(+), 8 deletions(-)
>
> On ARC, tst-tls-surplus passes, but it seems there's still some static TLS
> shenanigans.
>
> FAIL: elf/tst-tls-ie
> FAIL: elf/tst-tls-ie-dlmopen
>
> $ cat elf/tst-tls-ie.out
>
> maintls[1000]: 0x20026f80 .. 0x20027368
> var0[480]: 0x2093c648 .. 0x2093c828 global-dynamic
> var1[120]: 0x2093cc40 .. 0x2093ccb8 global-dynamic
> var2[24]: 0x2093d0d0 .. 0x2093d0e8 global-dynamic
> var3[16]: 0x2093d500 .. 0x2093d510 global-dynamic
> error: xdlfcn.c:29: error: dlopen:
> glibc-2.31.9000-730-ge9422236a2dd4/build/elf/tst-tls-ie-mod4.so: cannot allocate
> memory in static TLS block
>
> cat elf/tst-tls-ie-dlmopen.out
> maintls[1000]: 0x20026f80 .. 0x20027368
> var0[480]: 0x2093c648 .. 0x2093c828 global-dynamic
> var1[120]: 0x2093d3d8 .. 0x2093d450 global-dynamic
> var2[24]: 0x2093e000 .. 0x2093e018 global-dynamic
> var3[16]: 0x2093ebc8 .. 0x2093ebd8 global-dynamic
> error: xdlmopen.c:28: error: dlmopen:
> glibc-2.31.9000-730-ge9422236a2dd4/build/elf/tst-tls-ie-mod6.so: cannot allocate
> memory in static TLS block
I looked at the binaries, but I do not see anything obviously wrong. I
think you need to single-step through the allocations to see where they
fail, sorry.
Thanks,
Florian
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
prev parent reply other threads:[~2020-07-20 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87eepaqsgk.fsf@oldenburg2.str.redhat.com>
2020-07-19 4:39 ` [PATCH v2] elf: Change TLS static surplus default back to 1664 Vineet Gupta
2020-07-20 14:33 ` Florian Weimer [this message]
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=878sfew90u.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.org \
/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 NNTP newsgroup(s).