From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Destructors not called for c++11 thread_local objects
Date: Fri, 01 Aug 2014 17:42:00 -0000 [thread overview]
Message-ID: <53DBD151.90308@cygwin.com> (raw)
In-Reply-To: <53DBCF39.9050309@cs.utoronto.ca>
On 08/01/2014 01:32 PM, Ryan Johnson wrote:
> Hi all,
>
> (Please CC me in replies, I'm not subscribed to the list)
>
> Question: is this a Cygwin bug, gcc bug, or somebody else's bug entirely?
>
> The following STC shows the problem:
>
> $ cat bug.cpp
> #include <cstdio>
> static thread_local struct X {
> int x;
> X() { puts("hi"); }
> ~X() { puts("bye!"); }
> } x;
> int main() { x.x = 0; }
>
> $ g++ -std=gnu++11 -Wall -g bug.cpp && ./a
> hi
>
> A quick inspection of the assembly code shows no call to __cxa_thread_atexit
> in __tls_init, where the same code compiled on linux, with the same version
> of gcc, has it right. This is odd, because the function does seem to be
> available in cygwin's libstdc++:
>
> $ nm /usr/lib/gcc/x86_64-pc-cygwin/4.8.3/libstdc++.a | grep thread_atexit
> 0000000000000000 d .data$_ZZ19__cxa_thread_atexitE4once
> 0000000000000000 p .pdata$__cxa_thread_atexit
> 0000000000000000 t .text$__cxa_thread_atexit
> 0000000000000000 r .xdata$__cxa_thread_atexit
> 0000000000000000 T __cxa_thread_atexit
> 0000000000000000 d _ZZ19__cxa_thread_atexitE4once
>
> Here's the linux version of __tls_init:
>> __tls_init:
>> .LFB19:
>> cmpb $0, %fs:__tls_guard@tpoff
>> je .L7
>> rep; ret
>> .L7:
>> subq $8, %rsp
>> movl $.LC1, %edi
>> movb $1, %fs:__tls_guard@tpoff
>> call puts
>> movq %fs:0, %rsi
>> movl $__dso_handle, %edx
>> movl $_ZN1XD1Ev, %edi
>> addq $8, %rsp
>> addq $_ZL1x@tpoff, %rsi
>> jmp __cxa_thread_atexit
> vs. the same for cygwin:
>> __tls_init:
>> subq $40, %rsp
>> leaq __emutls_v.__tls_guard(%rip), %rcx
>> call __emutls_get_address
>> cmpb $0, (%rax)
>> je .L27
>> addq $40, %rsp
>> ret
>> .L27:
>> leaq .LC0(%rip), %rcx
>> movb $1, (%rax)
>> addq $40, %rsp
>> jmp puts
>
> Relevant packages installed:
> binutils 2.24.51-4
> cygwin 1.7.30-1
> gcc-core 4.8.3-2
> gcc-g++ 4.8.3-2
> libstdc++6 4.8.3-2
>
> (I realize I'm a version behind on cygwin1.dll, but I don't think that's the
> problem here)
>
> Thoughts?
Well it's not a general gcc problem because the same code on Linux with
version 4.8.3 works for me.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-08-01 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 17:33 Ryan Johnson
2014-08-01 17:42 ` Larry Hall (Cygwin) [this message]
2014-08-01 18:17 ` Corinna Vinschen
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=53DBD151.90308@cygwin.com \
--to=reply-to-list-only-lh@cygwin.com \
--cc=cygwin@cygwin.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).