search for: sanctiti

On Jun 1, 2012, at 11:13 PM, Justin Holewinski wrote: >> In a way, they are. What if I want a debug trace in a multi-threaded context? Right now, all threads would just spew to the same stream and the result would be unreadable. If you allow threads to setup their own outs() and errs() streams (transparently to the rest of LLVM), you can intercept these as you see fit, perhaps dumping

On Sat, Jun 2, 2012 at 8:56 AM, Chris Lattner <clattner at apple.com> wrote: > On Jun 1, 2012, at 11:13 PM, Justin Holewinski wrote: > > In a way, they are. What if I want a debug trace in a multi-threaded >> context? Right now, all threads would just spew to the same stream and the >> result would be unreadable. If you allow threads to setup their own outs()

This is not, strictly speaking, an LLVM issue, but it is an implementation matter that a compiler using LLVM needs to handle. I've got resolutions for other platforms, but I'm not seeing how to get this done for PowerPC, and I'ld appreciate suggestions or pointers. For BitC procedures that require an environment pointer, our general approach has been to construct a heap-allocated

On Fri, Jun 1, 2012 at 10:17 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jun 1, 2012, at 7:41 PM, Justin Holewinski wrote: > > > >> > Unfortunately, the use of outs() and (especially) errs() is rampant - a >> simple grep of the 3.1 source tree shows about 1,500 instances. One of the >> first things we had to implement in order to make LLVM

If I may add my two cents: I am planning to use LLVM as the backend for a compiler I am working on. And I wholeheartedly agree with Justin that it is a problem, if LLVM is allowed to freely write to stdout and stderr as it is a component which can be used in all sorts of code, be it a GUI IDE, a CLI driver, or whatever. Also, I have a number of times wondered about the somewhat unusual use of

On Jun 1, 2012, at 7:41 PM, Justin Holewinski wrote: > > > > Unfortunately, the use of outs() and (especially) errs() is rampant - a simple grep of the 3.1 source tree shows about 1,500 instances. One of the first things we had to implement in order to make LLVM usable is something very similar to what Justin has proposed. Centralizing control of the output in outs()/errs() would

notice: /subject.sol1.net/virtual_mail_server/File[/etc/postfix]/checksum: checksum changed ''{time}Thu Jan 25 16:31:08 EST 2007'' to ''{time}Thu Jan 25 16:36:39 EST 2007'' I know there''s something weird in the directory modification detection that causes the next run after things actually change to suffer from this problem, but I''m getting it

Hey We have a static analyzer setup for Xen called Coverity. It allows the code to be inspected for bugs and such. Originally I setup this so that we could make sure that there are no bugs that cause security issues - and as such invited only folks on the security Xen mailing list. But there are other folks who I am sure would like to contribute and as Coverity is pretty amazing at analyzing