From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] Add missing crt0 symbols for RTEMS
Date: Mon, 05 Dec 2016 10:34:00 -0000 [thread overview]
Message-ID: <20161205103356.GB4078@calimero.vinschen.de> (raw)
In-Reply-To: <1480922571-7022-1-git-send-email-sebastian.huber@embedded-brains.de>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
Hi Sebastian,
On Dec 5 08:22, Sebastian Huber wrote:
> In order to enable proper detection of thread-local storage availability
> we have to provide some symbols on ARM.
>
> Signed-off-by: Sebastian Huber <sebastian.huber@embedded-brains.de>
> ---
> newlib/libc/sys/rtems/crt0.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/newlib/libc/sys/rtems/crt0.c b/newlib/libc/sys/rtems/crt0.c
> index 1a0a055..769cde7 100644
> --- a/newlib/libc/sys/rtems/crt0.c
> +++ b/newlib/libc/sys/rtems/crt0.c
> @@ -188,6 +188,11 @@ RTEMS_STUB(_VOID, _free_r(struct _reent *r, _PTR *p), { })
> /* stubs for functions required by libc/stdlib */
> RTEMS_STUB(void, __assert_func(const char *file, int line, const char *failedexpr), { })
>
> +#if defined(__arm__)
> +RTEMS_STUB(void, __aeabi_read_tp(void), { })
> +RTEMS_STUB(void *, __tls_get_addr(const void *ti), { })
> +#endif
> +
> /* The PowerPC expects certain symbols to be defined in the linker script. */
>
> #if defined(__PPC__)
> --
> 1.8.4.5
Shall I commit this even without the crt0.o problem fixed?
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-12-05 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 7:23 Sebastian Huber
2016-12-05 10:34 ` Corinna Vinschen [this message]
2016-12-05 14:35 ` Sebastian Huber
2016-12-05 15:46 ` Corinna Vinschen
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=20161205103356.GB4078@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.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).