public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains 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: Wed, 26 May 2010 14:12:00 -0000 [thread overview]
Message-ID: <20100526141214.30763.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44276-507@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from iains at gcc dot gnu dot org 2010-05-26 14:12 -------
(In reply to comment #4)
> This also occurs on hppa64-hp-hpux11.11.
OK, I've built gcc & newlib for cris-elf and it's apparent that we need to deal
with the fact that that aliased emutls symbols are named differently...
that is the user writes alias(foo) ... but the emulated tls system needs to
understand alias(__emutls_v.foo) )
I'll take a look at how to implement this...
.. sorry for this fallout from the other fix
The patch @ comment#24 of PR44132 also needs to understand this issue, and
won't solve this problem yet.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44276
next prev parent reply other threads:[~2010-05-26 14:12 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 [this message]
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
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=20100526141214.30763.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).