public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Joel Sherrill <joel@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] libc/sys/rtems/crt0.c: Fix two warnings.
Date: Thu, 17 Jun 2021 17:58:52 +0000 (GMT)	[thread overview]
Message-ID: <20210617175852.A605F39960ED@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=59584ff16b67e9bc34477d94001ba346ba186ffc

commit 59584ff16b67e9bc34477d94001ba346ba186ffc
Author: Joel Sherrill <joel@rtems.org>
Date:   Mon Jun 14 16:31:08 2021 -0500

    libc/sys/rtems/crt0.c: Fix two warnings.
    
            __assert_func() is marked as noreturn and stub should not.
            __tls_get_addr() needed to return a value..

Diff:
---
 newlib/libc/sys/rtems/crt0.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/newlib/libc/sys/rtems/crt0.c b/newlib/libc/sys/rtems/crt0.c
index 6b8b5f98f..3b131d9c4 100644
--- a/newlib/libc/sys/rtems/crt0.c
+++ b/newlib/libc/sys/rtems/crt0.c
@@ -195,13 +195,13 @@ 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 *func, const char *failedexpr), { })
+RTEMS_STUB(void, __assert_func(const char *file, int line, const char *func, const char *failedexpr), { while (1) ;})
 
 #if defined(__arm__)
 RTEMS_STUB(void, __aeabi_read_tp(void), { })
 #endif
 
-RTEMS_STUB(void *, __tls_get_addr(const void *ti), { })
+RTEMS_STUB(void *, __tls_get_addr(const void *ti), { return NULL; })
 
 /* The PowerPC expects certain symbols to be defined in the linker script. */


                 reply	other threads:[~2021-06-17 17:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210617175852.A605F39960ED@sourceware.org \
    --to=joel@sourceware.org \
    --cc=newlib-cvs@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).