search for: antixlabs

Hello, I am looking to employ a graduate developer who can demonstrate experience of working with the LLVM technology and community and who is willing to take on an exciting and challenging role at Antix Labs limited. There is a job spec posted on our web site: http://antixlabs.com/aboutUs/vacancies.html If you are interested, or would like to know more, please contact us through recruitment at antixlabs.com with your CV and a covering letter. Thanks and regards, Mike Foss Chief Operating Officer Antix Labs Ltd. 200 Brook Drive, Green Park, Reading, Berk...

On 9/20/07, Richard Smith <richard.smith at antixlabs.com> wrote: > Many thanks. Yes, this question has slightly sidetracked on the license > issue, which was mostly an aside as to why we wish to use something other > than Cygwin. > I totally understand. :-) I just wanted to bring it back on a technical track. > On the make issue, I...

Hi, I'm looking at writing a custom backend targetting a proprietary virtual machine. I'm basing it on the existing C and MSIL backends. The VM has a defined ABI for varargs functions: the caller allocates some memory to hold the arguments and passes a pointer to this memory as an extra parameter in the call. I'd like to write a varargs lowering pass that represents this ABI

Hi, I'm using LLVM 2.0 on cygwin and x86_64-linux-gnu. If I compile a simple program using setjmp: #include <setjmp.h> extern jmp_buf j; extern void g(void); int f(void) { volatile int v = 0; if (setjmp(j)) return v; v = 1; g(); return 0; } the resulting bitcode doesn't use LLVM's exception handling intrinsics, it just has a call to a function called

Hi Anton, > > I would expect llvm-gcc to use LLVM's setjmp/longjmp intrinsics and > > then to run the LowerSetJmp pass to turn the intrinsic calls into uses > > of invoke and unwind. At that point, the control flow is explicit, > > isn't it? > Unfortunately, no. You can call setjmp/longjmp on the same jump buffer > multiple times. So, in general it's not

llvm-gcc-4.2-2.3.source.tar.gz contains the gcc/testsuite/ directory. llvm-gcc4.2-2.2.source.tar.gz didn't. Is that intentional? Thanks, Jay.

> I'm linking a program (my ellsif driver) that basically brings in most > of the LLVM stuff: bitcode reading, optimizations, linking, and target > code generation. > > All of a sudden, I'm getting the following when I run: > [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions > -O5 > <premain>: CommandLine Error: Argument

I wrote some code that fell over when it encountered this ConstantExpr: i32 add (i32 24, i32 ptrtoint ([20 x %"struct.stlpmtx_std::string"]* @_ZN12BulletMLNode11name2stringE to i32))) because it expected the LHS of the add to be another ConstantExpr. (This is the first time that bit of code has fallen over, despite having compiled thousands of test cases and many megabytes of C and

I tried building LLVM 2.1 with no real target CPU backends enabled, just the C backend, by hacking the configure script slightly: --- /home/foad/llvm/llvm-2.1/configure 2007-09-17 22:37:52.000000000 +0100 +++ configure 2007-12-13 10:29:41.000000000 +0000 @@ -4762,7 +4762,7 @@ done ;; esac -TARGETS_TO_BUILD="CBackend MSIL $TARGETS_TO_BUILD"

Hi, I'm looking at writing a custom backend targetting a proprietary virtual machine. I'm basing it on the existing C and MSIL backends. My VM only has 32- and 64-bit integer operations (like the JVM) but C code compiled with llvmgcc typically has lots of 1-, 8- and 16-bit instructions. I was thinking of writing a custom pass to promote small integer types and instructions to 32-bits,

Hi, Various parts of LLVM seem to assume that the ABI for a varargs function is compatible with the ABI for a non-varargs function, so that code like this: define void @f(i32 %x) { ... } ... call void (...)* bitcast (void (i32)* @f to void (...)*)(i32 42) will work. (I don't think C guarantees that this will work, at least not in the version of the C99 standard I checked.) I'm

I am working on a port of LLVM targeting a proprietary VM. Thus far development has been under Linux and Cygwin. Cygwin licensing would appear to require that LLVM built under Cygwin would have to be released under the GPL, so alternatives are being investigated. Using MS Visual Studio and following the instructions at http://llvm.org/docs/GettingStartedVS.html (Getting Started with the LLVM

I have a question about the llvm debugging records, especially wrt compile units. In the non-LLVM sense, a compile unit is essentially everything contained within a single .o file, and it is derived from one or more source and header files. Included in a compile unit are functions and global data. Dwarf records refer to compile units in the same way: a compile unit record has children which