On 3/31/06, Mike Stump <[EMAIL PROTECTED]> wrote:
> On Mar 30, 2006, at 7:55 AM, Camm Maguire wrote:
> > This was the most promising. If I could run gcc as a pipe with
> > assembler only output, all I need is a 'flush instruction on stdin
> > to get the assemly of the function(s) input thus far.
>
On Mar 30, 2006, at 7:55 AM, Camm Maguire wrote:
Longer term, it would be nice to have someone from your camp
layout where the time is spent and what changes might be worth
while in gcc to make it more suitable for that type of work.
This would be interesting, how does one benchmark gcc per
Greetings, and thanks for your reply!
Mike Stump <[EMAIL PROTECTED]> writes:
> On Mar 25, 2006, at 9:14 PM, Camm Maguire wrote:
> > Greetings! GCL is a lisp compiler system which outputs C code normally
> > compiled by gcc into an object, which is then loaded and relocated
> > into the running G
On Mar 25, 2006, at 9:14 PM, Camm Maguire wrote:
Greetings! GCL is a lisp compiler system which outputs C code normally
compiled by gcc into an object, which is then loaded and relocated
into the running GCL image. In lisp, compiling is a very incremental
process, with many, often thousands of s
Camm Maguire writes:
> Greetings! GCL is a lisp compiler system which outputs C code normally
> compiled by gcc into an object, which is then loaded and relocated
> into the running GCL image. In lisp, compiling is a very incremental
> process, with many, often thousands of small functions com
