Flavio Cruz, le dim. 30 avril 2023 19:47:27 -0400, a ecrit:
> The only difference with the previous patch is that we use mig_strlen so
> that we can pick __mig_strlen when building glibc.
Why doing so? For memcpy we have glibc's
sysdeps/mach/include/mach/mig_support.h #define memcpy to __mig_memcp
Dynamically sized strings can be represented as c_string[*] (*). We inline
up to 64 bytes but can pass arbitrary strings if needed out of line. Currently
implementation is limited to input arguments only (MiG will error out if
used as output).
In the user stub, we first run mig_strlen on the param
Hello
On Fri, Apr 28, 2023 at 5:08 AM Sergey Bugaev wrote:
> On Fri, Apr 28, 2023 at 6:00 AM Flavio Cruz wrote:
> > Dynamically sized strings can be represented as c_string[*] (*). We
> inline
> > up to 64 bytes but can pass arbitrary strings if needed out of line.
> Currently
> > implementatio
Sergey Bugaev, le ven. 28 avril 2023 12:08:16 +0300, a ecrit:
> (As I understand it, Debian ships old glibc but fresh MIG.)
Yes, but I backport whatever patch is needed.
Samuel
On Fri, Apr 28, 2023 at 6:00 AM Flavio Cruz wrote:
> Dynamically sized strings can be represented as c_string[*] (*). We inline
> up to 64 bytes but can pass arbitrary strings if needed out of line. Currently
> implementation is limited to input arguments only (MiG will error out if
> used as outp
Dynamically sized strings can be represented as c_string[*] (*). We inline
up to 64 bytes but can pass arbitrary strings if needed out of line. Currently
implementation is limited to input arguments only (MiG will error out if
used as output).
In the user stub, we first run strlen on the parameter
