This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: David Abdurachmanov <david dot abd at gmail dot com>
To: Andreas Schwab <schwab at suse dot de>
Cc: gcc-patches at gcc dot gnu dot org, Stefan O'Rear <sorear2 at gmail dot com>
Date: Tue, 20 Mar 2018 13:13:38 +0100
Subject: Re: [PATCH] Backport of RISC-V support for libffi
References: <mvm7eq7hvhi.fsf@suse.de> <1521543889.12197.18.camel@gmail.com> <mvm370vhul9.fsf@suse.de>

On Tue, 2018-03-20 at 12:09 +0100, Andreas Schwab wrote:
> On Mär 20 2018, David Abdurachmanov <david.abd@gmail.com> 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?

I don't know about significance of GOARCH, but I do care about
consistency with golang port to avoid confusion by users later on.

I have not filed a bug report. I though Stefan (CC) was in contact with
you regarding this.

david

References:
- [PATCH] Backport of RISC-V support for libffi
  - From: Andreas Schwab
- Re: [PATCH] Backport of RISC-V support for libffi
  - From: David Abdurachmanov
- Re: [PATCH] Backport of RISC-V support for libffi
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]