On Tue, Jun 27, 2017 at 7:54 PM, Joseph Myers <jos...@codesourcery.com> wrote:
> On Tue, 27 Jun 2017, Joseph Myers wrote:
>
>> Current glibc no longer gives the ucontext_t type the tag struct
>> ucontext, to conform with POSIX namespace rules.  This requires
>> various linux-unwind.h files in libgcc, that were previously using
>> struct ucontext, to be fixed to use ucontext_t instead.  This is
>> similar to the removal of the struct siginfo tag from siginfo_t some
>> years ago.
>>
>> This patch changes those files to use ucontext_t instead.  As the
>> standard name that should be unconditionally safe, so this is not
>> restricted to architectures supported by glibc, or conditioned on the
>> glibc version.
>>
>> Testing compilation together with current glibc with glibc's
>> build-many-glibcs.py.  OK to commit (mainline and active release
>> branches) if that passes?

Ok to commit to trunk.  Please wait for a while before backporting to catch
non-glibc and ancient glibc issues.

Thanks,
Richard.

> That compilation testing has now passed (together with a couple of glibc
> patches, now committed, to fix the build with -Wmultistatement-macros).
>
> --
> Joseph S. Myers
> jos...@codesourcery.com

Reply via email to