search for: granvillebarnett

...with LLVM use the foundation in place, however, I am curious as to whether there are any IDE projects that are building further upon this. Granville On Tue, Jun 16, 2009 at 7:47 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Tue, Jun 16, 2009 at 6:04 AM, Granville > Barnett<granvillebarnett at googlemail.com> wrote: > > Hi, > > I seem to remember that a big point of LLVM being built with tooling > support > > out of the box was a major thing, however, I've not read anything about > any > > tools which are actually taking advantage of the foundation...

On Tue, Jun 16, 2009 at 6:04 AM, Granville Barnett<granvillebarnett at googlemail.com> wrote: > Hi, > I seem to remember that a big point of LLVM being built with tooling support > out of the box was a major thing, however, I've not read anything about any > tools which are actually taking advantage of the foundation LLVM provides. > I'm n...

Hi, I seem to remember that a big point of LLVM being built with tooling support out of the box was a major thing, however, I've not read anything about any tools which are actually taking advantage of the foundation LLVM provides. I'm not a Mac user, but I'd assume XCode would be a prime candidate - does/will XCode use LLVMs foundation to create a better IDE experience? Also, anyone

...Hi Granville, I'm not aware of anything publicly announced that is taking advantage of this yet. -Chris > > Granville > > On Tue, Jun 16, 2009 at 7:47 PM, Bill Wendling <isanbard at gmail.com> > wrote: > On Tue, Jun 16, 2009 at 6:04 AM, Granville > Barnett<granvillebarnett at googlemail.com> wrote: > > Hi, > > I seem to remember that a big point of LLVM being built with > tooling support > > out of the box was a major thing, however, I've not read anything > about any > > tools which are actually taking advantage of the founda...

On Thu, Jun 18, 2009 at 3:14 AM, Granville Barnett<granvillebarnett at googlemail.com> wrote: > >> Firstly, rather than using a single 1 word pointer to represent a >> reference I >> chose to use 3 words including a pointer to the type and a pointer to the >> value (as well as metadata). This allows typed nulls and that addresses an &g...

> > That is similar to the approach I used, although HLVM provides a pointer directly to the type, saving you a single hop. I'm not so sure that is a very good reason, depending on your implementation data structures that are fundamental to the type system of the virtual machine use custom allocators so the extra hop carries little to no expense. I would not have considered it had I

On Thursday 18 June 2009 12:28:57 Cory Nelson wrote: > I'm also curious what language uses this and why it is useful :) HLVM is intended to be a general-purpose VM rather than a particular language. > Also, things like this would make lock-free algorithms difficult or > impossible. True. Perhaps that is a good argument for providing both kinds. However, nulls are certainly more

> Firstly, rather than using a single 1 word pointer to represent a reference > I > chose to use 3 words including a pointer to the type and a pointer to the > value (as well as metadata). This allows typed nulls and that addresses an > important deficiency found in most other VMs including the CLR. Is Scarcity > able to handle such references or does its implementation of stack

Hi, I've not got any experience using ANTLR to parse C++, however, you will find that there only exists a C code generator for ANTLR and NOT a C++ one. Over the years numerous people have requested a C++ code generation template but alas there is still only a C one. Just a heads up. Granville 2009/7/11 Vikram S. Adve <vadve at cs.uiuc.edu> > We are looking for an open source C++

Are there any papers in the works which benchmark some specification suite of C programs on GCC, LLVM-GCC, and CLANG? The only stuff I have seen so far are some bar charts in a few LLVM presentations, would be nice to have something a little more comprehensive. Cheers, Granville On Tue, Jun 16, 2009 at 6:51 AM, Jon Harrop <jon at ffconsultancy.com> wrote: > On Tuesday 16 June 2009

When you create a parser via ANTLR you specify the output language of the resulting recursive descent parser, at the moment there exists no C++ output template to my knowledge, thus you would have to generate the parser as C code for which a template exists. The runtime support should be there, at least partially but it won't use things like exceptions, nor will it have a very modular design