From: Joel Sherrill <joel@rtems.org>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: [PATCH] RTEMS: Include missing header and fix stub
Date: Fri, 13 Mar 2020 13:26:30 -0500 [thread overview]
Message-ID: <CAF9ehCWuY-jT89jV_EhatubSvPgpN0=beuX3s-VSrwMMx3-aUg@mail.gmail.com> (raw)
In-Reply-To: <20200313172136.10663-1-sebastian.huber@embedded-brains.de>
This is OK and RTEMS specific. I will push it.
--joel
On Fri, Mar 13, 2020 at 12:21 PM Sebastian Huber <
sebastian.huber@embedded-brains.de> wrote:
> Signed-off-by: Sebastian Huber <sebastian.huber@embedded-brains.de>
> ---
> newlib/libc/sys/rtems/crt0.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/newlib/libc/sys/rtems/crt0.c b/newlib/libc/sys/rtems/crt0.c
> index 28db7132a..6b8b5f98f 100644
> --- a/newlib/libc/sys/rtems/crt0.c
> +++ b/newlib/libc/sys/rtems/crt0.c
> @@ -13,6 +13,7 @@
> #include <sys/lock.h>
> #include <sys/stat.h>
> #include <sys/uio.h>
> +#include <assert.h>
> #include <reent.h>
> #include <signal.h>
> #include <stdlib.h>
> @@ -194,7 +195,7 @@ RTEMS_STUB(void *, _malloc_r(struct _reent * r, size_t
> s), { return 0; })
> RTEMS_STUB(void, _free_r(struct _reent *r, void *p), { })
>
> /* stubs for functions required by libc/stdlib */
> -RTEMS_STUB(void, __assert_func(const char *file, int line, const char
> *failedexpr), { })
> +RTEMS_STUB(void, __assert_func(const char *file, int line, const char
> *func, const char *failedexpr), { })
>
> #if defined(__arm__)
> RTEMS_STUB(void, __aeabi_read_tp(void), { })
> --
> 2.16.4
>
>
prev parent reply other threads:[~2020-03-13 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 17:21 Sebastian Huber
2020-03-13 18:26 ` Joel Sherrill [this message]
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='CAF9ehCWuY-jT89jV_EhatubSvPgpN0=beuX3s-VSrwMMx3-aUg@mail.gmail.com' \
--to=joel@rtems.org \
--cc=newlib@sourceware.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).