From: Ian Lance Taylor <iant@google.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: ColdFire and Thread-Local Storage
Date: Tue, 28 Jan 2014 19:15:00 -0000 [thread overview]
Message-ID: <CAKOQZ8yGOWKD3d7waw0f7ucaStHENQ16X=EMntnKBsG45JpG3w@mail.gmail.com> (raw)
In-Reply-To: <52E7D186.4030108@embedded-brains.de>
On Tue, Jan 28, 2014 at 7:49 AM, Sebastian Huber
<sebastian.huber@embedded-brains.de> wrote:
>
> it seems GCC uses this ColdFire TLS ABI:
>
> https://lists.debian.org/debian-68k/2007/11/msg00071.html
>
> Here we have a function
>
> void *__m68k_read_tp(void)
>
> which must return the thread pointer in register a0.
>
> I have to implement this function. Is there a way to instruct GCC to return
> the value in register a0 instead of d0 or do I have to use assembler to
> implement this function?
I believe that on m68k GNU/Linux a function that returns a pointer
will normally return the value in a0.
Ian
next prev parent reply other threads:[~2014-01-28 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 15:49 Sebastian Huber
2014-01-28 19:15 ` Ian Lance Taylor [this message]
2014-01-29 7:51 ` Sebastian Huber
2014-01-29 19:50 ` Norbert Lange
2014-01-30 10:43 ` Sebastian Huber
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='CAKOQZ8yGOWKD3d7waw0f7ucaStHENQ16X=EMntnKBsG45JpG3w@mail.gmail.com' \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=sebastian.huber@embedded-brains.de \
/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).