[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <C7LPPDEK9MIU.2E0M7RCVVZ08V@taiga>
Date: Sun, 06 Dec 2020 12:49:25 GMT
From: "Drew DeVault" <sir@...wn.com>
To: "Szabolcs Nagy" <nsz@...t70.net>
Cc: <musl@...ts.openwall.com>
Subject: Re: [PATCH v2] riscv64: correct struct __ucontext name
On Sun Dec 6, 2020 at 3:51 AM EST, Szabolcs Nagy wrote:
> * Drew DeVault <sir@...wn.com> [2020-12-05 18:10:06 +0000]:
> > This makes it consistent with other architectures and fixes some issues
> > with downstream software.
>
> which software?
>
> glibc uses struct ucontext_t too and user code should use ucontext_t
> without struct.
libucontext, which does use ucontext_t.
In fact, the issue was more related to the type conflict with
ucontext.h, which declared struct __ucontext in the scope of its
function declarations due to the naming mismatch.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
