From: Jiong Wang <jiong.wang@arm.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Marcus Shawcroft <marcus.shawcroft@gmail.com>,
gcc-patches <gcc-patches@gnu.org>
Subject: Re: [AArch64][TLSLE][3/3] Implement local executable mode for all memory model
Date: Thu, 27 Aug 2015 10:34:00 -0000 [thread overview]
Message-ID: <n991tep3v59.fsf@arm.com> (raw)
In-Reply-To: <n9961413w63.fsf@arm.com>
Jiong Wang writes:
>>>
>>> Those relocation types required by tls-size 12 & 24 are supported by
>>> binutils-2.25 already, and you have passed compilation and failed at
>>> exectuion, so there do have something wrong I guess.
>>>
>>> Either the generated instruction sequence or the bare-metal environment.
>>>
>>> One thing strange to me is those testcases are guarded by:
>>>
>>> /* { dg-require-effective-target tls_native } */
>>>
>>> while for bare-metal environment, normally you don't have tls_native
>>> support right? then these testcases should have been marked as
>>> unsupported otherwise they will generate native tls instruction
>>> sequences while the bare-metal runtime environment may don't support
>>> initialize tp register etc, thus caused the exectuion error.
>>>
>>> Could you please double check this? thanks
>>>
>>
>> Well, the "tls_native" check passes (there is no "emutls" string in
>> the generated assembly).
>> This BTW, does not involve the binutils, since it only check the
>> assembly output.
>>
>> Could it be a configure error instead? (where GCC wouldn't notice that
>> it shouldn't generate such relocations)
>
> to me, it's more like this. native tls is enabled on a no such support
> platform.
>
> I am trying to setup a bare-metal environment for reproducing. I was
> testing on linux environment.
Finished test on my local aarch64-none-elf bare-metal. they are marked
as unsupported correctly. gcc is doing correct configuration on my
environment. looks like somehow gcc is doing wrong tls enable on your
bare-metal platform.
UNSUPPORTED: gcc.target/aarch64/tlsdesc_hoist.c
UNSUPPORTED: gcc.target/aarch64/tlsle12_1.c
UNSUPPORTED: gcc.target/aarch64/tlsle24_1.c
UNSUPPORTED: gcc.target/aarch64/tlsle32_1.c
--
Regards,
Jiong
next prev parent reply other threads:[~2015-08-27 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 16:58 [AArch64][TLSLE][N/N] " Jiong Wang
2015-06-26 16:02 ` Marcus Shawcroft
2015-08-19 14:50 ` [AArch64][TLSLE][3/3] " Jiong Wang
2015-08-25 9:50 ` Marcus Shawcroft
2015-08-27 7:52 ` Christophe Lyon
2015-08-27 9:21 ` Jiong Wang
2015-08-27 9:41 ` Christophe Lyon
2015-08-27 9:53 ` Jiong Wang
2015-08-27 10:34 ` Jiong Wang [this message]
2015-08-27 13:23 ` Christophe Lyon
2015-08-27 13:36 ` Jiong Wang
2015-08-27 13:45 ` Christophe Lyon
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=n991tep3v59.fsf@arm.com \
--to=jiong.wang@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gnu.org \
--cc=marcus.shawcroft@gmail.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).