public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46131] Some TLS execution tests fail on Tru64 UNIX with emutls
Date: Fri, 22 Oct 2010 14:59:00 -0000 [thread overview]
Message-ID: <20101022145900.D7NqsuCS5aUW1OWBm7OfzJPYw6c7AQJnP7uFbtHm5o0@z> (raw)
In-Reply-To: <bug-46131-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46131
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2010-10-22 14:59:32 UTC ---
> --- Comment #3 from Richard Henderson <rth at gcc dot gnu.org> 2010-10-22 14:51:59 UTC ---
> I don't see anything wrong in the assembler code for
> the test case. I think you'll need to debug the libgcc
> routines to see what's going wrong in between there and
> the system thread library.
Ok, I'll have a look. This will have to wait for a couple of days since
I'll be away on a short vacation in a few minutes.
Rainer
next prev parent reply other threads:[~2010-10-22 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 14:37 [Bug middle-end/46131] New: " ro at gcc dot gnu.org
2010-10-22 14:37 ` [Bug middle-end/46131] " ro at gcc dot gnu.org
2010-10-22 14:38 ` ro at gcc dot gnu.org
2010-10-22 14:52 ` rth at gcc dot gnu.org
2010-10-22 14:59 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2010-10-28 14:26 ` [Bug target/46131] " ro at gcc dot gnu.org
2010-10-28 14:43 ` ro at gcc dot gnu.org
2010-11-02 16:07 ` ro at gcc dot gnu.org
2010-11-02 16:12 ` ro at gcc dot gnu.org
2010-11-02 16:23 ` ro at gcc dot gnu.org
2010-12-06 17:28 ` ro 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=20101022145900.D7NqsuCS5aUW1OWBm7OfzJPYw6c7AQJnP7uFbtHm5o0@z \
--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).