Re: [PATCH] Backport of RISC-V support for libffi go closures

2018-08-14 Thread Jim Wilson
On 08/14/2018 02:00 AM, Andreas Schwab wrote: Backport of RISC-V support for libffi go closures * src/riscv/ffi.c (ffi_call_go, ffi_prep_go_closure): New functions. (ffi_call_int): Renamed from ffi_call. (ffi_call_asm, ffi_closure_inner): Adjust interface.

Re: [PATCH] Backport of RISC-V support for libffi

2018-05-04 Thread Jim Wilson
On 03/20/2018 03:50 AM, Andreas Schwab wrote: This is a backport of (the only difference to upstream is s/FFI_ALIGN/ALIGN/, as we don't have commit bd72848c7a). This is needed for libgo. OK. You might have to update the patch, as at least o

Re: [PATCH] Backport of RISC-V support for libffi

2018-03-20 Thread David Abdurachmanov
On Tue, 2018-03-20 at 12:09 +0100, Andreas Schwab wrote: > On Mär 20 2018, David Abdurachmanov wrote: > > > What is the current situation/resolution regarding GOARCH? GCC use > > RISCV64, but golang port uses RISCV. It would be nice to have a > > resolution before GCC 8 release is cut. > > I did

Re: [PATCH] Backport of RISC-V support for libffi

2018-03-20 Thread Andreas Schwab
On Mär 20 2018, David Abdurachmanov wrote: > What is the current situation/resolution regarding GOARCH? GCC use > RISCV64, but golang port uses RISCV. It would be nice to have a > resolution before GCC 8 release is cut. I didn't know that GOARCH has any significance. Did you file a bug? Andrea

Re: [PATCH] Backport of RISC-V support for libffi

2018-03-20 Thread David Abdurachmanov
I am using the same changes in Fedora RISC-V with GCC 8.0.1-0.19 (libffi patch + s/FFI_ALIGN/ALIGN/ + regen). Note that libffi port is missing go closures support. Small things like hello world work fine, but utilities like "go" will complain with run- time error: fatal error: libgo built without