public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikestump at comcast dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/52268] tls support should be added for darwin11 Date: Thu, 16 Feb 2012 17:20:00 -0000 [thread overview] Message-ID: <bug-52268-4-pBhOeANSh8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52268-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52268 --- Comment #1 from Mike Stump <mikestump at comcast dot net> 2012-02-16 17:15:47 UTC --- If you could snapshot some codegen, say void foo() { static __thread int i = 42; ++i; } or somesuch, we could see if they wired it up the same was as gcc is normally wired. I suspect it should be fairly close. I'm thinking this should be easy to wire up.
next prev parent reply other threads:[~2012-02-16 17:17 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-16 4:02 [Bug target/52268] New: " howarth at nitro dot med.uc.edu 2012-02-16 6:30 ` [Bug target/52268] " howarth at nitro dot med.uc.edu 2012-02-16 17:20 ` mikestump at comcast dot net [this message] 2012-02-16 19:01 ` iains at gcc dot gnu.org 2012-02-29 17:44 ` howarth at nitro dot med.uc.edu 2012-03-01 1:28 ` howarth at nitro dot med.uc.edu 2012-03-01 1:29 ` howarth at nitro dot med.uc.edu 2012-03-01 14:15 ` howarth at nitro dot med.uc.edu 2014-06-20 21:15 ` egall at gwmail dot gwu.edu 2014-06-30 5:44 ` jeremyhu at macports dot org 2014-06-30 8:17 ` iains at gcc dot gnu.org 2014-06-30 17:55 ` jeremyhu at macports dot org 2014-07-30 11:36 ` [Bug target/52268] native " egall at gwmail dot gwu.edu 2021-07-09 23:04 ` egallager 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=bug-52268-4-pBhOeANSh8@http.gcc.gnu.org/bugzilla/ \ --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).