[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH glibc] Stop checking if MiG supports retcode.

From: Flávio Cruz
Subject: Re: [PATCH glibc] Stop checking if MiG supports retcode.
Date: Mon, 15 May 2023 00:09:44 -0400

Hi Sergey

On Wed, May 10, 2023 at 1:36 AM Sergey Bugaev <bugaevc@gmail.com> wrote:

On Wed, May 10, 2023, 08:21 Flavio Cruz <flaviocruz@gmail.com> wrote:
> HAVE_MIG_RETCODE is removed completely since this will be a no-op either
> way (compiling against old Hurd headers will work the same, new Hurd
> headers will result in the same stubs since retcode is a no-op).

It is a no-op currently, but please note that I was planning to make
it not a no-op some time (I wanted my epoll server to return error
replies properly). Will that cause any issues?

No, it should be fine. For that functionality, maybe we should enforce that the return code
parameter is always the second parameter (after the reply port - which is already the
case) by adding the appropriate checks in MiG when retcode is used. If we want
./configure to check if MiG generates code to call the server reply routine
in case of errors (it doesn't :() then we will need to build a different check.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]