public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/44276] [4.6 Regression]: gcc.dg/tls/alias-1.c
Date: Thu, 27 May 2010 01:15:00 -0000 [thread overview]
Message-ID: <20100527011516.24094.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44276-507@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from hp at gcc dot gnu dot org 2010-05-27 01:15 -------
(In reply to comment #8)
> One thing you could help with is whether there's a way of enabling threads on
> the simulator
You mean "for cris-axis-elf"; no, there is no support for threads on
cris-axis-elf.
(I could reply "yes" to your original question, however, but that's irrelevant;
the simulator supports cris-axis-linux-gnu too, but you don't want to build for
that target, it's a slightly more complicated. :)
Let's hope your patch gets reviewed post haste.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44276
next prev parent reply other threads:[~2010-05-27 1:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 18:38 [Bug middle-end/44276] New: " hp at gcc dot gnu dot org
2010-05-25 18:41 ` [Bug middle-end/44276] " hp at gcc dot gnu dot org
2010-05-25 19:15 ` iains at gcc dot gnu dot org
2010-05-25 20:38 ` iains at gcc dot gnu dot org
2010-05-26 12:56 ` danglin at gcc dot gnu dot org
2010-05-26 14:12 ` iains at gcc dot gnu dot org
2010-05-26 20:26 ` iains at gcc dot gnu dot org
2010-05-27 0:13 ` hp at gcc dot gnu dot org
2010-05-27 0:49 ` iains at gcc dot gnu dot org
2010-05-27 1:15 ` hp at gcc dot gnu dot org [this message]
2010-05-27 10:12 ` iains at gcc dot gnu dot org
2010-06-24 21:33 ` rguenth at gcc dot gnu dot org
2010-07-13 20:31 ` iains at gcc dot gnu dot org
2010-07-13 23:07 ` hp at gcc dot gnu dot org
2010-08-11 10:24 ` iains at gcc dot gnu dot org
2010-08-11 13:15 ` dave at hiauly1 dot hia dot nrc dot ca
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=20100527011516.24094.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: 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).