search for: keithsheppard

...omething that I haven't ever done before so I could use some pointers. Is there a recipe for building LLVM for raspberry pi that someone can share or any pointers? Incase it matters the source OS is OS X Mountain Lion and I'm happy to use gcc/clang/whatever works. Thanks, Keith -- http://keithsheppard.name

...e somewhat new MD functions). Is there a reason that some functions ask for length? If possible, I'd prefer for the API not to require length for reasons of simplicity and consistency and if it turns out that there is consensus for this change I'm happy to prepare a patch. Best, Keith -- keithsheppard.name -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121031/4cbc0896/attachment.html>

...keith/bin The LLVM bindings are generated by my F# code so they are not in the repo, but here is the Target binding for example: <https://gist.github.com/997985> Do you have any ideas for what I need to fix in order for initializeNativeTarget to work? Thanks for any suggestions, Keith -- keithsheppard.name

...so I could use some pointers. Is there > a recipe for building LLVM for raspberry pi that someone can share or > any pointers? Incase it matters the source OS is OS X Mountain Lion > and I'm happy to use gcc/clang/whatever works. > > Thanks, Keith > > -- > > http://keithsheppard.name > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

...nice, consistent way. It allowed me to autogen most of the bindings which makes for a more complete binding coverage with hopefully fewer bugs. One disappointment with the C API is that LLVMInitializeNativeTarget is declared static so it can't be used by bindings like llvm-fs. Best, Keith -- keithsheppard.name

Hello, Does anyone know how to build LLVM for the i386 architecture with snow leopard (this seems to have been the default for leopard). I've tried building with: ./configure CFLAGS="-arch i386" CXXFLAGS="-arch i386" LDFLAGS="-arch i386" OBJCFLAGS="-arch i386" --prefix=/Users/keith/share/ --enable-shared --enable-jit && make but I still end up

Hi Keith, > Hello, Does anyone know how to build LLVM for the i386 architecture > with snow leopard (this seems to have been the default for leopard). > I've tried building with: > > ./configure CFLAGS="-arch i386" CXXFLAGS="-arch i386" LDFLAGS="-arch > i386" OBJCFLAGS="-arch i386" --prefix=/Users/keith/share/ > --enable-shared

Hi Mikael, > 2. LLVM.NET/LLVM-F# <http://LLVM.NET/LLVM-F#> uses the C API. Are there > anything important missing from this API, things that are only accessible > through the C API? there's lots missing from the C API because functionality is added when someone needs it. In the other direction, there's nothing the C binding can do that the C++ API can't as far as

...ctly onto the C++ API, some methods map to a sequence of C++ calls. > > Ciao, Duncan > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -- keithsheppard.name

Hi, I am a newbie in LLVM. I am very impressed with this forum and appreciate your help and time. I am trying to include llvm IR parser in my codebase, the way I wanna do is generate llvm's shared object (.so) file and use it in my project. So far I haven't been able to generate correct .so's. When I build a debug build with gmake (have llvm and clang in my sandbox), I get the

Hi, I have decided against coding my planned Braceless compiler in C++ and have instead opted for using the .NET bindings that Keith Shephard have made using F# (a .NET language). This leads to two questions: 1. Is it okay if I adapt the Kalaidoscope tutorial to C# and we include the adapted version in the LLVM.NET distro and on the LLVM.NET website? I have written very clearly that Chris

...cfe-dev at cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev >> > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -- keithsheppard.name

On Fri, Apr 6, 2012 at 6:15 PM, Alan Garny <agarny at hellix.com> wrote: > Hi, > > From what I have seen on this mailing list and elsewhere, it would seem that > it isn’t possible to build LLVM as a shared library using Visual C++. Still, > I would imagine that quite a few people are or would be interested in it, > so… is there any plan to support this any time soon? This,

You might want to mention other functionality, like Herald, which I think fills a need that a lot of developers have. Well, I guess since this message is on the list, I can just say: Phabricator's "Herald" tool lets you (among other things) set up actions to happen in response to certain events; one huge use case for this is setting up alerts when parts of the tree that you are

Hi, >From what I have seen on this mailing list and elsewhere, it would seem that it isn't possible to build LLVM as a shared library using Visual C++. Still, I would imagine that quite a few people are or would be interested in it, so. is there any plan to support this any time soon? This, unless it's already supported in some way or another which I am not aware of.? I have been

Dear LLVM / Clang community, we'd like to open the use of Phabricator as an optional tool for doing code reviews to a wider audience. Please feel free to start your code reviews by following the documentation at http://llvm.org/docs/Phabricator.html. Note that e-mail is still the reference medium for code reviews. Please let me know about any problems with Phabricator or the documentation