public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@redhat.com>
To: Kito Cheng <kito.cheng@gmail.com>
Cc: Newlib <newlib@sourceware.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
		Andrew Waterman <andrew@sifive.com>,
	patches@groups.riscv.org
Subject: Re: Newlib/libgloss port for RISC-V
Date: Mon, 31 Jul 2017 17:34:00 -0000	[thread overview]
Message-ID: <CAOox84vm6+nCNSa1aDROUJgXJMentreipYYfyTk+uBk2X-t4Lw@mail.gmail.com> (raw)
In-Reply-To: <CA+yXCZCi-5q=64XcUcPwwDSUt-HrY4-W4MXu9wDTNZ1z-9HMbg@mail.gmail.com>

Hi Kito,

Before I continue reviewing, I have noticed that you have no licensing
information in any of your non-generated files.  You need to add this
as Red Hat has
the default license.  You can make it BSD-like or see other licenses
in the repository that are even more permissive.  That said, you have
another issue in that one of your files (asm.h) in the first patch has
been taken from glibc and is LPGL.  This can cause problems unless you
are building newlib as a dynamic library as code that links to your
library becomes LGPL unless it provides everything required to relink.
  See:  https://stackoverflow.com/questions/10130143/gpl-lgpl-and-static-linking

My suggestion would be to create your own version of asm.h and any
other files that are LGPL and license them how you see fit.

Regards,

-- Jeff J.

On Thu, Jul 27, 2017 at 5:29 AM, Kito Cheng <kito.cheng@gmail.com> wrote:
> Hi all:
>
> We'd like to contribute for RISC-V[1] support to newlib/libgloss.
> RISC-V is an open ISA which support both 32 and 64 bit.
>
> For the other part of GNU toolchain, GCC and binutils already included
> in upstream in GCC 7 / binutils 2.28.
>
> We've also tested with newlib and gcc testsuite for following targets:
>
> riscv32-unknown-elf
> riscv64-unknown-elf
>
> [PATCH 1/3] Add RISC-V port for newlib
> https://sourceware.org/ml/newlib/2017/msg00669.html
> [PATCH 2/3] Add RISC-V port for libm
> https://sourceware.org/ml/newlib/2017/msg00670.html
> [PATCH 3/3] Add RISC-V port for libgloss
> https://sourceware.org/ml/newlib/2017/msg00671.html
>
> Contributor list:
>    - Andrew Waterman  <andrew@sifive.com>
>    - Kito Cheng  <kito.cheng@gmail.com>
>    - Palmer Dabbelt  <palmer@dabbelt.com>
>    - Scott Beamer  <sbeamer@eecs.berkeley.edu>
>    - Michael Neilly  <mneilly@yahoo.com>
>    - Alex Suykov  <alex.suykov@gmail.com>
>
>
> [1] https://riscv.org/

  reply	other threads:[~2017-07-31 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27  9:29 Kito Cheng
2017-07-31 17:34 ` Jeff Johnston [this message]
2017-08-01  2:36   ` [patches] " Kito Cheng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOox84vm6+nCNSa1aDROUJgXJMentreipYYfyTk+uBk2X-t4Lw@mail.gmail.com \
    --to=jjohnstn@redhat.com \
    --cc=andrew@sifive.com \
    --cc=kito.cheng@gmail.com \
    --cc=newlib@sourceware.org \
    --cc=palmer@dabbelt.com \
    --cc=patches@groups.riscv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).