public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47715] [x32] TLS doesn't work
Date: Sun, 13 Feb 2011 17:41:00 -0000	[thread overview]
Message-ID: <bug-47715-4-Q3tkbVUgru@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47715-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47715

--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> 2011-02-13 17:01:13 UTC ---
Another one:

[hjl@gnu-6 ilp32-14]$ cat s.c
struct initial_sp
{
  void *sp;
  long len;
};
__thread struct initial_sp __morestack_initial_sp;
void bar (void *);
void
foo ()
{
  bar (&__morestack_initial_sp.len);
}
[hjl@gnu-6 ilp32-14]$ make s.s
/export/build/gnu/gcc-x32/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/gcc-x32/build-x86_64-linux/gcc/ -S -o s.s -mx32 -O2 -g
-fPIC    s.c
s.c: In function \u2018foo\u2019:
s.c:12:1: error: unrecognizable insn:
(insn 8 7 9 3 (set (reg/f:SI 59)
        (const:SI (plus:SI (symbol_ref:SI ("__morestack_initial_sp") [flags
0x10] <var_decl 0x7f9e580eb000 __morestack_initial_sp>)
                (const_int 4 [0x4])))) s.c:11 -1
     (nil))
s.c:12:1: internal compiler error: in extract_insn, at recog.c:2109
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [s.s] Error 1
[hjl@gnu-6 ilp32-14]$


  parent reply	other threads:[~2011-02-13 17:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-13  0:59 [Bug target/47715] New: " hjl.tools at gmail dot com
2011-02-13  1:49 ` [Bug target/47715] " hjl at gcc dot gnu.org
2011-02-13 17:41 ` hjl.tools at gmail dot com [this message]
2011-02-13 23:36 ` hjl at gcc dot gnu.org
2011-02-14 18:48 ` hjl at gcc dot gnu.org
2011-02-17 14:32 ` hjl.tools at gmail dot com
2011-02-18  2:50 ` hjl at gcc dot gnu.org
2011-02-25 17:25 ` hjl.tools at gmail dot com
2011-02-25 21:46 ` hjl.tools at gmail dot com
2011-02-25 21:49 ` hjl at gcc dot gnu.org
2011-05-15 23:21 ` hjl at gcc dot gnu.org
2011-06-29 16:40 ` hjl at gcc dot gnu.org
2011-07-05 15:48 ` hjl at gcc dot gnu.org
2011-07-28  2:43 ` hjl.tools at gmail dot com
2011-07-28  2:45 ` hjl.tools at gmail dot com
2011-07-28 14:43 ` uros at gcc dot gnu.org
2011-07-29 13:49 ` uros at gcc dot gnu.org
2011-07-29 13:52 ` ubizjak at gmail dot com
2011-07-29 16:44 ` hjl at gcc dot gnu.org
2011-07-29 16:56 ` hjl at gcc dot gnu.org
2011-08-06 14:26 ` hjl at gcc dot gnu.org
2011-08-06 14:50 ` hjl 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-47715-4-Q3tkbVUgru@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).