On Sun, Mar 06, 2022 at 10:22:56AM -0500, Rich Felker wrote:
> On Mon, Feb 21, 2022 at 09:25:43AM -0800, Ian Lance Taylor via Gcc-patches
> wrote:
> > Note for gofrontend-dev: on gcc-patches only Andreas Schwab suggested
> > using uc_regs instead of regs, which does look correct to me.
>
> Yes, t
On Mon, Feb 21, 2022 at 09:25:43AM -0800, Ian Lance Taylor via Gcc-patches
wrote:
> Note for gofrontend-dev: on gcc-patches only Andreas Schwab suggested
> using uc_regs instead of regs, which does look correct to me.
Yes, this is absolutely the correct fix. Having pt_regs appear at all
in code n
What would be the benefit of using .uc_regs instead of .regs? The
current code works entirely fine as it, it just needs an include of the
Linux Kernel header defining the pt_regs type (which my proposed patch
adds).
Furthermore, it seems to me that .uc_regs is only available on powerpc
but not on
Note for gofrontend-dev: on gcc-patches only Andreas Schwab suggested
using uc_regs instead of regs, which does look correct to me.
Ian
On Mon, Feb 21, 2022 at 8:47 AM Sören Tempel wrote:
>
> Ping.
>
> Summary: Fix build of libgo on PPC with musl libc and libucontext by
> explicitly including th
On Jan 02 2022, soeren--- via Gcc-patches wrote:
> libgo/runtime/go-signal.c: In function 'getSiginfo':
> libgo/runtime/go-signal.c:227:63: error: invalid use of undefined type
> 'struct pt_regs'
> 227 | ret.sigpc =
> ((ucontext_t*)(context))->uc_mcontext.regs->nip;
Ping.
Summary: Fix build of libgo on PPC with musl libc and libucontext by
explicitly including the Linux header defining `struct pt_regs` instead of
relying on other libc headers to include it implicitly.
See: https://gcc.gnu.org/pipermail/gcc-patches/2022-January/587520.html
If the patch needs
