search for: obsurd

...tr, but it will solve the problem. However, later on: > > ExpandKadds(line, eline) > > Where eline is the same size as line. I think the real solution is to make > sure the buffer is larger (LOG_LINE_LENGTH) like Michal said, and make sure > modules and programs don't generate obsurdly long messages, because you > can't be certain how much room is necessary for the expanded symbols. It > would be nice if ExpandKadds() allocated memory dynamically, but it doesn't. RedHat immediately issued a "fix" to their current package: sysklogd-1.3-26 This "fix...

...guarantee that it happens. We will eventually allow the front-end to mark a call as being a tail call, but noone has implemented this yet (it shouldn't be hard). In any case, the optimizer is pretty agressive about eliminating tail calls, so you probably won't run into problems except for obsurd situations. Writing a scheme front-end for LLVM sounds like a great project: please keep us informed how it goes, and when it gets mostly functional, let us know so we can add a link on the web site. :) -Chris -- http://llvm.cs.uiuc.edu/ http://www.nondot.org/~sabre/Projects/

Hi, 1. A small question: How do I ensure memory alignment? I want all malloced memory, globals and functions to be 4-byte aligned. Does llvm have any ".align" keyword? I'm currently implementing a small scheme toy-compiler, and want to use the lowest 2 bits for type tags. It's Currently 380 lines of scheme-code[1], quite similar to the compiler in SICP[2], which I hope to get