Displaying 3 results from an estimated 3 matches for "mcpeak".
2007 Dec 22
0
[LLVMdev] [Oink-devel] Status of Elsa->LLVM
> I've build gcc many times over the years for different target processors
> and was never able to get my head around it internally. It is incredibly
> complex. I also didn't like the fact that I had to have N copies of gcc
> to support N processors.
Scott McPeak is rather familiar with the internals of gcc and edg and
says elsa is far simpler.
> I became interested in Elsa (via google) because I liked its extensible
> nature. I can drop in new syntax rules easily. It was also fairly easy
> to understand.
We worked very hard to make it that way j...
2007 Dec 23
1
[LLVMdev] [Oink-devel] Status of Elsa->LLVM
...> I've build gcc many times over the years for different target processors
>> and was never able to get my head around it internally. It is incredibly
>> complex. I also didn't like the fact that I had to have N copies of gcc
>> to support N processors.
>
> Scott McPeak is rather familiar with the internals of gcc and edg and
> says elsa is far simpler.
I agree, very much.
>
>> I became interested in Elsa (via google) because I liked its extensible
>> nature. I can drop in new syntax rules easily. It was also fairly easy
>> to understand...
2007 Dec 22
5
[LLVMdev] Status of Elsa->LLVM
Chris Lattner wrote:
> On Dec 21, 2007, at 1:08 PM, Richard Pennington wrote:
>
>> I'm a little further along now. I've started to put together a simple
>> driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think
>> it works).
>>
>> The file being compiled is a "printf" function. Here are timing
>> results