public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52268] New: tls support should be added for darwin11
Date: Thu, 16 Feb 2012 04:02:00 -0000 [thread overview]
Message-ID: <bug-52268-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52268
Bug #: 52268
Summary: tls support should be added for darwin11
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: howarth@nitro.med.uc.edu
The clang compiler in clang 3.0 and Xcode 4.2 currently provides tis support on
darwin11. This same ability to generate the required tis assembly for darwin11
should be added to FSF gcc.
next reply other threads:[~2012-02-16 3:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 4:02 howarth at nitro dot med.uc.edu [this message]
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
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@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: 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).