public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44132] [4.6 Regression] emutls is broken under a range of circumstances.
Date: Sat, 15 May 2010 13:48:00 -0000 [thread overview]
Message-ID: <20100515134815.26412.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44132-19002@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from hubicka at ucw dot cz 2010-05-15 13:48 -------
Subject: Re: [4.6 Regression] emutls is broken under a
range of circumstances.
> I'd rather go with the DECL_PRESERVE_P hack for now.
Problem with this is that emultls is still broken with LTO. As soon as we
merge multiple emultls vars from multiple units, we will screw up at expansion
time.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44132
next prev parent reply other threads:[~2010-05-15 13:48 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 6:59 [Bug target/44132] New: " iains at gcc dot gnu dot org
2010-05-14 8:17 ` [Bug target/44132] " iains at gcc dot gnu dot org
2010-05-14 12:25 ` rguenth at gcc dot gnu dot org
2010-05-15 8:26 ` iains at gcc dot gnu dot org
2010-05-15 8:29 ` iains at gcc dot gnu dot org
2010-05-15 8:40 ` hubicka at ucw dot cz
2010-05-15 8:59 ` iains at gcc dot gnu dot org
2010-05-15 9:26 ` iains at gcc dot gnu dot org
2010-05-15 9:35 ` hubicka at ucw dot cz
2010-05-15 11:24 ` iains at gcc dot gnu dot org
2010-05-15 11:32 ` rguenth at gcc dot gnu dot org
2010-05-15 11:57 ` iains at gcc dot gnu dot org
2010-05-15 13:48 ` hubicka at ucw dot cz [this message]
2010-05-15 13:49 ` hubicka at ucw dot cz
2010-05-15 15:40 ` iains at gcc dot gnu dot org
2010-05-17 20:22 ` iains at gcc dot gnu dot org
2010-05-17 20:32 ` iains at gcc dot gnu dot org
2010-05-18 1:40 ` iains at gcc dot gnu dot org
2010-05-18 9:10 ` iains at gcc dot gnu dot org
2010-05-18 15:56 ` iains at gcc dot gnu dot org
2010-05-18 16:55 ` dominiq at lps dot ens dot fr
2010-05-19 10:39 ` ro at gcc dot gnu dot org
2010-05-19 14:48 ` iains at gcc dot gnu dot org
2010-05-24 14:37 ` iains at gcc dot gnu dot org
2010-05-24 17:28 ` iains at gcc dot gnu dot org
2010-05-24 20:12 ` iains at gcc dot gnu dot org
2010-05-25 9:39 ` iains at gcc dot gnu dot org
2010-05-27 20:12 ` iains at gcc dot gnu dot org
2010-05-27 22:02 ` jakub at gcc dot gnu dot org
2010-05-27 22:52 ` iains at gcc dot gnu dot org
2010-06-02 20:35 ` jakub at gcc dot gnu dot org
2010-06-02 20:41 ` iains at gcc dot gnu dot org
2010-06-03 1:11 ` howarth at nitro dot med dot uc dot edu
2010-06-03 9:22 ` iains at gcc dot gnu dot org
2010-06-03 14:52 ` dominiq at lps dot ens dot fr
2010-06-03 15:03 ` iains at gcc dot gnu dot org
2010-06-03 15:22 ` dominiq at lps dot ens dot fr
2010-06-03 16:09 ` iains at gcc dot gnu dot org
2010-06-03 20:57 ` dominiq at lps dot ens dot fr
2010-06-03 23:45 ` iains at gcc dot gnu dot org
2010-06-04 18:25 ` dominiq at lps dot ens dot fr
2010-06-04 18:46 ` iains at gcc dot gnu dot org
2010-07-03 16:45 ` iains at gcc dot gnu dot org
2010-07-09 23:40 ` rth at gcc dot gnu dot org
2010-07-26 22:54 ` rth at gcc dot gnu dot org
2010-07-26 22:59 ` rth at gcc dot gnu dot org
[not found] <bug-44132-4@http.gcc.gnu.org/bugzilla/>
2021-11-28 4:37 ` pinskia 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=20100515134815.26412.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).