From: Nick Clifton <nickc@redhat.com>
To: Galit.Heller@nsc.com
Cc: binutils@sources.redhat.com
Subject: Re: Port to binutils without assembler
Date: Thu, 17 Jul 2003 15:33:00 -0000 [thread overview]
Message-ID: <m33ch5ji4k.fsf@redhat.com> (raw)
In-Reply-To: <3F1404F9.3FC87967@nsc.com> (Galit Heller's message of "Tue, 15 Jul 2003 16:43:21 +0300")
Hi Galit,
> I'm a member of a team at National Semiconductor, which develops
> and supports a development toolset for National Semiconductor's
> CompactRISC CPUs. The compiler, linker and debugger are a gnu based
> port (currently for CR16C).
>
> We are planning to begin the process of submitting the port -
> initially to binutils - and we have a preliminary question:
> can we submit to binutils w/o the assembler ?
This is actually quite a complex question. One the hand, the FSF is
very reluctant to accept any contributions which will make a user
reliant on proprietary software. Their goal is to free software from
ownership and instead put it in the public domain. So although a
binutils linker for the CR16C might be nice, on its own it is not
enough to create a free set of tools for the architecture.
On the other hand, by accepting and making available a free linker,
the binutils project might encourage CompactRISC CPU users to develop
and release a port of GAS as well. Thereby achieving the goal of a
completely free set of binary utilities for the architecture.
> This is because the assembler is currently not ported to gnu.
Does this mean that you do have plans to port GAS to the CompactRISC
architecture ? If so, do you also plan to contribute this port
if/when it is complete ?
> We would be willing to assign the assembler's (proprietary) source
> code to the FSF under GPL, if this were to help.
It would certainly help. With a free assembler, even if it is not
GAS, a programmer would be able to obtain a completely free set of
binary tools for the CR16C, which matches the FSF goals in this area.
So - in conclusion - yes the binutils project would be prepared to
accept a CR16C linker contribution, provided that:
a. The appropriate FSF copyright assignments were made
& b. A free assembler was also available. (This does not have to be
GAS, although that would be nice).
Cheers
Nick Clifton
Binutils Head Maintainer
prev parent reply other threads:[~2003-07-17 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 13:45 Galit Heller
2003-07-17 15:33 ` Nick Clifton [this message]
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=m33ch5ji4k.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=Galit.Heller@nsc.com \
--cc=binutils@sources.redhat.com \
/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).