From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Ian Lance Taylor <iant@google.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: ColdFire and Thread-Local Storage
Date: Wed, 29 Jan 2014 07:51:00 -0000 [thread overview]
Message-ID: <52E8B2FE.5040102@embedded-brains.de> (raw)
In-Reply-To: <CAKOQZ8yGOWKD3d7waw0f7ucaStHENQ16X=EMntnKBsG45JpG3w@mail.gmail.com>
On 2014-01-28 20:15, Ian Lance Taylor wrote:
> 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
>
The function
void *__m68k_read_tp(void)
{
const Thread_Control *executing = _Thread_Get_executing();
return (char *) executing->Start.tls_area +
_TLS_Get_thread_control_block_area_size((uintptr_t) _TLS_Alignment)
+ 0x7000;
}
translates to
__m68k_read_tp:
move.l #_TLS_Alignment,%d0
moveq #8,%d1
move.l _Per_CPU_Information+18,%a0
cmp.l %d0,%d1
jls .L2
moveq #8,%d0
.L2:
add.l #28672,%d0
add.l 194(%a0),%d0
rts
I use now:
void __m68k_read_tp(void)
{
const Thread_Control *executing = _Thread_Get_executing();
void *tp = (char *) executing->Start.tls_area +
_TLS_Get_thread_control_block_area_size((uintptr_t) _TLS_Alignment)
+ 0x7000;
__asm__ volatile (
"move.l %0, %%a0"
:
: "d" (tp)
);
}
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
next prev parent reply other threads:[~2014-01-29 7:51 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
2014-01-29 7:51 ` Sebastian Huber [this message]
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=52E8B2FE.5040102@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
/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).