public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gary at intrepid dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/28141] thread-local ptr initialized to address of thread-local misclassified as non-constant initializer Date: Fri, 23 Jun 2006 16:48:00 -0000 [thread overview] Message-ID: <20060623164431.8364.qmail@sourceware.org> (raw) In-Reply-To: <bug-28141-9975@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from gary at intrepid dot com 2006-06-23 16:44 ------- I agree this is definitely an enhancement, but will note the following: 1. On Fedora Core 5, x86_64, I was able to successfully link and run a null program (written in assembly) that initializes thread local 'ptr' that points to thread local 'data'. The declarations appear as follows: .globl data .section .tbss,"awT",@nobits .align 8 .type data, @object .size data, 8 data: .zero 8 .globl ptr .align 8 .type ptr, @object .size ptr, 8 ptr: .quad data I didn't run extensive tests to verify this was doing the right thing, but there were no complaints from the linker. 2. Given that __thread is an extension, we could choose to interpret "constancy", as "constant from the perspective of the currently executing thread" without doing much harm to "C" semantics. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28141
next prev parent reply other threads:[~2006-06-23 16:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-06-23 6:55 [Bug c/28141] New: " gary at intrepid dot com 2006-06-23 7:04 ` [Bug c/28141] " pinskia at gcc dot gnu dot org 2006-06-23 16:48 ` gary at intrepid dot com [this message] [not found] <bug-28141-4@http.gcc.gnu.org/bugzilla/> 2024-04-03 23:20 ` pinskia at gcc dot gnu.org
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=20060623164431.8364.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).