search for: blantant

...ample, right now I'm looking at http://llvm.org/nightlytest/machine.php?machine=230. "CVS checkout time" might be wrong, as LLVM is now in SVN. This column also jitters heavily. However, it's not really important. "Configure time CPU": is always 0, which must be a blantant lie :-) "Build time CPU" is usually higher than "Build time wall". Isn't wall=cpu+system, so do we have negative system times here? I could be completely wrong, but this looks strange. However, for the Dejagnu test, it hold's that CPU time < wall time. Now I...

I gave a short presentation on LLVM for a couple of people here, and they had questions I could not immediately answer. The questions are rather obvious, so I'm hoping that someone has already found out the answers. So here we go: 1) What is the relative size of LLVM bitcode files and the corresponding native binaries? Are there significant differences between targets (e.g. x86, ARM,

On May 12, 2008, at 2:59 AM, Pertti Kellomäki wrote: > 2) What is the relative performance of code generated by LLVM > and gcc respectively? See llvm.org/nightlytest Many testers run various benchmarks and produces comparison numbers daily. > I am not looking for exact answers, rough ballpark figures > are quite sufficient. - Devang

Hi the list people, hi Ezra, I just read from this message http://rubyforge.org/pipermail/backgroundrb-devel/2006-July/000134.html that BackgrounDRb will offer a way to kill a worker from within itself. As this message is from 7/25, I wonder if this feature has been added since. If not, is there any way to do it? I tried this: MiddleMan.delete_worker(@_job_key) But it raise: uninitialized

...se CentOS, a free redistribution of RHEL (where Red Hat doesn't see a dime), are not complaining about Linus & co. for the kernel, not complaining about the CIPE team and their lack of movement on kernel 2.6, not volunteering to even look at the Bugzilla reports to find out what issues were blantantly repeatable, let alone other distros that have the same issues ... But blaming solely Red Hat for this issue (and this is just one example). But I expect that because some people just blame Microsoft for things outside of their control too. Sometimes the only person to blame is the lack of inte...