search for: modula3

(Moving this to llvm-dev) On Friday, October 16, 2015, Justin Bogner <mail at justinbogner.com> wrote: > Some users of llvm-c want stable API interfaces into various parts of > the LLVM infrasture, others want further ABI guarantees about this > usage, and still others simply want a way to bind to LLVM through their > language frontend’s existing FFI support for C. > > If

...hope to have a good idea of what people are actually >> using >> these APIs for, and both to support stable API users less haphazardly >> and to make unstable API more thorough and/or easier to create. >> >> > One actual use: > > A couple of us in the Modula3 support community are working on splicing a > llvm back end onto our Modula3 compiler front end. We have zero-thickness > bindings written in Modula3 which match C bindings like core.h. In our > front > end executable, we only build llvm IR in memory, then use > LLVMPrintModuleToFi...

I'm getting the bus error mentioned in PR bin/124353 and I need a bit more detail on how to apply the patch. Right now I'm getting the following error when I try to do a make on cvsup-without-gui: Fatal Error: bad version stamps: SupTCP.m3 I put the changes in the /usr/local/lib/m3/pkg/m3core/src/unix/freebsd-4.amd64/Unix.i3 file I created the file

> On 2014-Dec-05, at 00:39, Peter Collingbourne <peter at pcc.me.uk> wrote: > > On Thu, Dec 04, 2014 at 06:44:36PM -0800, Duncan P. N. Exon Smith wrote: >> As of Monday, I finally got a preliminary patch passing check and >> check-clang with the metadata-value split. > > Do you have the Go bindings enabled? Because of the changes you made to the > DIBuilder

CVSup is slow, insecure, and a memory hog. However, until now it's been the only option for keeping an up-to-date ports tree, and (thanks to all of the recent work on vuxml and portaudit) it has become quite obvious that keeping an up-to-date ports tree is very important. To provide a secure, lightweight, and fast alternative to CVSup, I've written portsnap. As the name suggests, this