🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.dsp
Article #2667

Re: SHARC G21K compiler sources?

#2667
From: Vince Del Vecchio
Date: Tue, 07 Jul 1998 00:00
67 lines
2985 bytes
	<6nq2gl$p5i$2@sun27.hrz.tu-darmstadt.de>
	<35A0A36B.358C49E1@unidata.se>
	<6nqq2m$ai5$1@sun27.hrz.tu-darmstadt.de>
	<%R6Wo1MdTy@draugen.kvaleberg.no>
Date: 07 Jul 1998 11:41:49 -0400
Message-ID: <nb4u34t8y82.fsf@dejavu.spd.analog.com>
Organization: Analog Devices CPD
Lines: 57
X-Newsreader: Gnus v5.3/Emacs 19.33

Without commenting on ADI's actions wrt the GPL, let me say a few
things.

Egil Kvaleberg <egil@kvaleberg.no> writes:

> On 6 Jul 1998, Uwe Bonnes wrote:
> 
> > has anybody bought these sources and is willing to share?
> 
> I have, and anyone may pick them up at:
> 
> 	ftp://ftp.sn.no/user/egilk/g21k-rel3.0.tar.gz
> 
> ...
>
> BTW, my order took months to process, and you'd have to fork out $150 for
> every new version of the compiler. I wonder how far the GPL can be 
> stretched in this respect?  

How long ago did you order/receive the sources you just posted?
They appear to be pretty ancient.

>       a. Assembler.
>       b. Linker/librarian.
>       c. C library, including signal processing functions.
>       d. Debugger.
> 
> AFAIK, AD uses their own linker and assembler. I assume that it would 
> be possible to port GNU stuff, but DSPs tends to be rather different from
> conventional processors, so it is probably a rather big job. The C-like
> syntax of the AD assemblers would also create difficulties, I'd say.

It is certainly true that just having the compiler sources is not
sufficient to do development.  The linker and assembler are home-grown.
I'm not sure porting GNU ld would be terribly difficult, although I have
no direct experience.  The assembler syntax, as you point out, is
decidedly non-traditional.

I believe the C library, including sources, is shipped with the
development tools package.  It certainly has no GPL'd code in it.

> WRT the debugger, the AD debugger seems to contain parts of GDB.
> This should mean that they would have to supply the source code for the
> entire debugger, it pressed. Alas, I have not had the time to investigate 
> this any further.

I don't know enough about the debugger to comment.

It is worth mentioning that almost all of the pieces you mention
(including the compiler) have either been replaced in the 4.0
(VisualDSP) release, or will soon be replaced.  (The one exception is
the runtime library.)

-Vince Del Vecchio
vince . delvecchio @ analog . com
Compiler Engineer
Working but not speaking for Analog Devices
Technical Details
Message-ID: <6ntfa1$78m@nwd2nws1.analog.com>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <358EEDCA.1A66@compuserve.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f8fcc,1443ffa9802045b3
X-Google-Attributes: gidf8fcc,public
X-Google-Thread: 1025b4,1443ffa9802045b3
X-Google-Attributes: gid1025b4,public
From: Vince Del Vecchio <vince.delvecchio@see-below.analog.com>
Subject: Re: SHARC G21K compiler sources?
Date: 1998/07/07
Message-ID: <6ntfa1$78m@nwd2nws1.analog.com>
X-Deja-AN: 369256072
References: <358EEDCA.1A66@compuserve.com>
Organization: analog.com
Newsgroups: comp.dsp,gnu.misc.discuss