From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [patch] problems with nucleus/types.h
Date: Fri, 21 Oct 2005 19:43:40 +0200 [thread overview]
Message-ID: <435928CC.1050205@domain.hid> (raw)
In-Reply-To: <4358A63B.6030907@domain.hid>
Jan Kiszka wrote:
> Hi,
>
> after the latest changes in include/nucleus/types.h, I get some warnings
> during userspace lib compilation on my box:
>
> In file included from /usr/src/xenomai/include/nucleus/queue.h:24,
> from /usr/src/xenomai/include/nucleus/timer.h:24,
> from /usr/src/xenomai/include/nucleus/thread.h:24,
> from
> /usr/src/xenomai/skins/native/lib/../../native/task.h:27,
> from /usr/src/xenomai/skins/native/lib/timer.c:21:
> /usr/src/xenomai/include/nucleus/types.h: In function
> 'xnobject_create_name':
> /usr/src/xenomai/include/nucleus/types.h:99: warning: implicit
> declaration of function 'snprintf'
> /usr/src/xenomai/include/nucleus/types.h:99: warning: incompatible
> implicit declaration of built-in function 'snprintf'
>
> This is due to the static inline definition of xnobject_create_name in
> the mentioned header and missing a snprintf prototype in userspace.
>
> What about the attached patch? It also avoids duplicating code by using
> strncpy (or am I overseeing a specific reason for doing it the other way?).
>
Applied, since types.h must be usable with as little deps as possible in order
to grab types and definitions. Thanks.
> Jan
>
>
> ------------------------------------------------------------------------
>
> Index: include/nucleus/types.h
> ===================================================================
> --- include/nucleus/types.h (revision 54)
> +++ include/nucleus/types.h (working copy)
> @@ -76,26 +76,16 @@
>
> #define XNOBJECT_NAME_LEN 32
>
> -static inline void xnobject_copy_name (char *dst,
> - const char *src)
> -{
> - if (src)
> - {
> - const char *rp = src;
> - char *wp = dst;
> - do
> - *wp++ = *rp;
> - while (*rp && rp++ - src < XNOBJECT_NAME_LEN);
> - }
> - else
> - *dst = '\0';
> -}
> +#define xnobject_copy_name(dst, src) \
> +do { \
> + if (src) \
> + strncpy(dst, src, XNOBJECT_NAME_LEN); \
> + else \
> + *dst = '\0'; \
> +} while (0)
>
> -static inline int xnobject_create_name(
> - char *dst, size_t n, void *obj)
> -{
> - return snprintf(dst, n, "%p", obj);
> -}
> +#define xnobject_create_name(dst, n, obj) \
> + snprintf(dst, n, "%p", obj)
>
> #define minval(a,b) ((a) < (b) ? (a) : (b))
> #define maxval(a,b) ((a) > (b) ? (a) : (b))
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
--
Philippe.
prev parent reply other threads:[~2005-10-21 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 8:26 [Xenomai-core] [patch] problems with nucleus/types.h Jan Kiszka
2005-10-21 17:43 ` Philippe Gerum [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=435928CC.1050205@domain.hid \
--to=rpm@xenomai.org \
--cc=kiszka@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.