From: Philippe Gerum <rpm@xenomai.org>
To: Giulio Moro <giulio@bela.io>
Cc: Florian Bezdeka <florian.bezdeka@siemens.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
xenomai@xenomai.org
Subject: Re: [xenomai4] POSIX API
Date: Fri, 22 Nov 2024 14:58:21 +0100 [thread overview]
Message-ID: <87jzcve5fm.fsf@xenomai.org> (raw)
In-Reply-To: <d276fea7-2873-6014-aea3-acced9943f7a@bela.io> (Giulio Moro's message of "Wed, 20 Nov 2024 14:34:56 -0500")
Giulio Moro <giulio@bela.io> writes:
> Thanks for sharing this with the list.
>
>>>> __real_frob() would require explicit call via some macro trick like
>>>> __STD() with libcobalt. Others would be invoked under the hood via a
>>>> plain call to frob(), depending on the insertion of liboverride.so
>>>> _before_ libposix.so on the linker command line.
>
> I am not sure I have a full grasp of the suggested approach, but I'll
> share a request for clarification/feature. On Xenomai 3 it is
> currently possible to avoid link-time wrapping and explicitly calling
> the `__wrap_func()` version, while regular `func()` calls result in
> the stock version (equivalent to `__real_func()`). I find this
> behaviour useful and would like it to be preserved in Xenomai 4. I
> hope this will still be possible for at least some combination of
> build flags.
>
Yes, this will be preserved for x4. The approach I'd like to see should
prefer explicit over implicit when it comes to wrapping, the use case
you described falls into this category.
--
Philippe.
prev parent reply other threads:[~2024-11-22 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ses62bi5.fsf@xenomai.org>
[not found] ` <d28b8d0200ef0e3ff63e833b64c2ad00c554e351.camel@siemens.com>
[not found] ` <878qthiw8i.fsf@xenomai.org>
[not found] ` <afea1670c26d61ccbd18b6a7b609498bb1dfb020.camel@siemens.com>
2024-11-20 13:43 ` [xenomai4] POSIX API Philippe Gerum
2024-11-20 19:34 ` Giulio Moro
2024-11-22 13:58 ` 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=87jzcve5fm.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=florian.bezdeka@siemens.com \
--cc=giulio@bela.io \
--cc=jan.kiszka@siemens.com \
--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.