public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] newlib: xstormy16: add missing string.h include
Date: Tue,  1 Mar 2022 06:15:53 +0000 (GMT)	[thread overview]
Message-ID: <20220301061553.5BDB93858D20@sourceware.org> (raw)

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

commit 644e8bba07cdb6ca47ebafc766b52951860721d4
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Tue Mar 1 01:14:33 2022 -0500

    newlib: xstormy16: add missing string.h include
    
    Some of these functions are using memcpy & memset from string.h but
    not including the header leading to implicit declaration warnings.

Diff:
---
 newlib/libc/machine/xstormy16/tiny-malloc.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/newlib/libc/machine/xstormy16/tiny-malloc.c b/newlib/libc/machine/xstormy16/tiny-malloc.c
index 597e389dc..e6f67a886 100644
--- a/newlib/libc/machine/xstormy16/tiny-malloc.c
+++ b/newlib/libc/machine/xstormy16/tiny-malloc.c
@@ -271,6 +271,8 @@ free (void *block_p)
 #endif
 
 #ifdef DEFINE_REALLOC
+#include <string.h>
+
 void *
 realloc (void *block_p, size_t sz)
 {
@@ -310,6 +312,8 @@ realloc (void *block_p, size_t sz)
 #endif
 
 #ifdef DEFINE_CALLOC
+#include <string.h>
+
 void *
 calloc (size_t n, size_t elem_size)
 {
@@ -509,6 +513,7 @@ pvalloc (size_t sz)
 
 #ifdef DEFINE_MALLINFO
 #include "malloc.h"
+#include <string.h>
 
 struct mallinfo 
 mallinfo (void)


                 reply	other threads:[~2022-03-01  6:15 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=20220301061553.5BDB93858D20@sourceware.org \
    --to=vapier@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).