search for: tamalpai

...A LLVM JIT compiler for x86 under 1 MB? I doubt it is possible without >> a major rewriting of LLVM. > > Even with no optimizations? Drat. That means I can't use it. Why? I'd never checked, but I always assumed the LLVM JIT was much larger than 3.4 MB. For comparison: [rnk at tamalpais google3]$ du -h /usr/lib/gcc/x86_64-linux-gnu/4.4/cc1plus 10M /usr/lib/gcc/x86_64-linux-gnu/4.4/cc1plus [rnk at tamalpais google3]$ du -h `which python2.6` 2.5M /usr/bin/python2.6 It seems reasonable that a JIT compiler with optimizers would weigh in somewhere between an interpreter and a full C+...

...and it works for me. With this source file t.c: #include <stdio.h> #include <stdlib.h> void baz() { printf("Hello, World!\n"); abort(); } void bar() { baz(); } void foo() { bar(); } int main(int argc, char **argv) { foo(); return 0; } Compiled like so: [rnk at tamalpais llvm]$ Debug/bin/clang -fexceptions t.c -c -emit-llvm -o t.bc -fexceptions is important when compiling C code, because otherwise the functions are annotated nounwind, which avoids generating .eh_frame dwarf. gdb uses the exception handling dwarf to unwind the stack. So long as your frontend doe...

I have followed http://llvm.org/docs/DebuggingJITedCode.html, used the latest release gdb-7.1 (from March 18, 2010) and got this stack: (gdb) bt #0 0x35532156 in ?? () #1 0x355320f8 in ?? () #2 0x35532098 in ?? () #3 0x3553202e in ?? () #4 0x34a5661a in ?? () #5 0x349d9bd9 in ?? () #6 0x08052cd9 in main (argc=4, argv=0xbfbfe264, envp=0xbfbfe278) at

> Why do you care about the size of library files? I assumed dynamic libraries and static libraries were similar in size, but I just checked some of my own static libraries and they are indeed much larger than the executables they compile to. Sorry, it just never occurred to me that they would be much different. > > Anyway, in the same example I mentioned that the size of HowToUseJIT

David Piepgrass <dpiepgrass at mentoreng.com> writes: >> Comparing the size of the static libraries makes little sense, and even >> less when they are compiled by different tools. What really matters is >> the size of the executables. >> >> I agree that LLVM can be considered a heavyweight dependency on this >> aspect. > > Why is the size of static

...ase, QA/QE, or UI engineering-- it would be a big plus. Previous startup experience would be great. Most importantly, we are looking for talented, driven people who are eager to work hard, learn quickly, and wear multiple hats. LOCATION: You will work in beautiful Marin County within view of Mt. Tamalpais, in our newly-renovated space featuring private offices, lots of sunlight and plenty of things nearby. We are located minutes from both the Golden Gate and Richmond bridges right off Hwy 101, making us within easy 20-30 minutes reach of San Francisco, East Bay, and North Bay. We enjoy all the ben...