SPARC native code compiler

Thread View: comp.lang.scheme.c

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by The Crossjammer Thu, 21 Jan 1993 20:09

#195

Author: The Crossjammer
Date: Thu, 21 Jan 1993 20:09

8 lines
904 bytes

I'm interested in porting the native code compiler to the SPARC
architecture if it hasn't been done already. Who should I contact?
--
xjam@cork.Berkeley.EDU  	Fiiiive Thousand Boomin Watts...... -The JBeez

They can't come on and play me in prime time, 	    | Free Millipede coin op
Cause I know the time, cause I'm gettin' mine.	    | and House music at my
I get on the mix late in the night... -Public Enemy | place! Drop by sometime.

Re: SPARC native code compiler

#200

Author: Guillermo J. Rozas
Date: Fri, 22 Jan 1993 17:06

39 lines
2189 bytes

In article <XJAM.93Jan21200905@cork.CS.Berkeley.EDU> xjam@cork.CS.Berkeley.EDU (The Crossjammer) writes:

|   From: xjam@cork.CS.Berkeley.EDU (The Crossjammer)
|   Newsgroups: comp.lang.scheme.c
|   Date: 21 Jan 93 20:09:05
|
|   I'm interested in porting the native code compiler to the SPARC
|   architecture if it hasn't been done already. Who should I contact?

To our knowledge, there is no back end for the Sparc architecture.

Depending on how much time you have, there are two possibilities.


Option A: Write a full native port.  To find out how to do this, ftp the
compiler porting guide from

altdorf.ai.mit.edu:archive/scheme-7.2/compdoc.tar.Z

It is very slightly out of date, but the differences should not be
important.

This will take a considerable amount of time (~3 weeks for an expert).


Option B: We have a back end that generates C almost finished.  It is
up enough to compile most of the runtime system (all but three files).
The output is both larger and slower than the native version, but much
faster than the interpreter.  Besides some debugging and cleaning up
of rough edges, one of the things that is missing is the ability to
load compiled files dynamically -- right now it is all done
statically, when the "microcode" is generated.  You could have a
working system much faster if you took this approach.


Even if you decide to go with option A, you may be interested in
option B as a reference.  The RTL rules expand into macroized-C
fragments rather than any individual architecture, so they may be
easier to understand.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads