search for: _too_

...then we can fix it. There are > much better ways to do this than templating the whole code emitter. > > That means JIT code also has the virtual function overhead too, this > will slow down existing JIT code. Templates are already there and > they work and they do not take up _too_ much memory. As I said before, if you are compelled to, feel free to continue with your approach of premature optimization. I will fix it later. -Chris

So, I'm trying to build everything from source for the Debian package for LLVM, including the C/C++ front end. I'm running this build on LLVM 1.4 source (the released tarball), using Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64 box, dual CPU). Before I get _too_ deep into it, I thought I would ask if the following compilation failure on the CFE looks the least bit familiar to anyone: /home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/xgcc -B/home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/ -B/usr/lib/llvm/cfrontend/x86_64-unknown-linux-gnu/bin/ -B/usr/lib/llvm/cfr...

...ound operators, tabifying, using C style comments). This patch could use some more work. It should only apply to decorated toplevels, but right now it also affects XUL menus (I guess because they are not unmanaged like in GTK?). It also affects the tab switcher window, which looks OK but a bit _too_ distracting IMHO. And finally sometimes visual artifacts are left on scree, though this may be simply my video drivers (nvidia binary geforce4 mx 440). Author unknown. Credit Quinn Storm. -------------- next part -------------- A non-text attachment was scrubbed... Name: minimize-scaler-mod.pat...

...natural result of the way the docs have grown over time. Presumably, part of the role of the Doc Support Group (DSG) is to hash out "better" organization, whatever that may be. Because the QSG is an overview, it would be best if the future structure of the whole set of docs isn''t _too_ hazy when the QSG is redone. Some possible design goals in this regard: (1) Keep the drill down layers on most topics or parameters limited, if possible, to say, three. Something like (a) overview/intro, (b) main doc, (c) detailed example, with the latter usually in file-specific docs/pages perha...

...ix it. There are much better >> ways to do this than templating the whole code emitter. >> >> That means JIT code also has the virtual function overhead too, this will >> slow down existing JIT code. Templates are already there and they work and >> they do not take up _too_ much memory. >> > > As I said before, if you are compelled to, feel free to continue with your > approach of premature optimization. I will fix it later. If you are not too bothered with the memory overhead in the short term then it is probably best to leave the code as it is for...

...o, I'm trying to build everything from source for the Debian > package for LLVM, including the C/C++ front end. I'm running > this build on LLVM 1.4 source (the released tarball), using > Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64 > box, dual CPU). Before I get _too_ deep into it, I thought I > would ask if the following compilation failure on the CFE > looks the least bit familiar to anyone: > > > /home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/xgcc > -B/home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/ > -B/usr/lib/llvm/cfrontend/x86_64-unknown...

...performance problem, then we can fix it. There are much better > ways to do this than templating the whole code emitter. > That means JIT code also has the virtual function overhead too, this will slow down existing JIT code. Templates are already there and they work and they do not take up _too_ much memory. > > Whats Daniels approach, does he have any online documentation or code, do > you have an email address so I may talk to him. > > > Take a look at how asmprinters work in include/llvm/Target/TargetRegistry.h > . If you have specific questions, llvmdev is a gr...

...hacker. He found a problem and a WFM-style fix, which at least improves the situation. By all means, replace the errno access with a jump to __syscall_error after setting up registers in a way that routine (from sysdeps/linux/cris/sysdep.S) expects it; I don?t know cris assembly but it doesn?t look _too_ hard? bye, //mirabilos -- FWIW, I'm quite impressed with mksh interactively. I thought it was much *much* more bare bones. But it turns out it beats the living hell out of ksh93 in that respect. I'd even consider it for my daily use if I hadn't wasted half my life on my zsh setup. :-)...

On Jul 16, 2009, at 12:53 AM, Aaron Gray wrote: > Chris, > > The basic idea of using templates inconjunction with inlining is for > efficiency. > > 6,500 virtual calls outputting bytes out of 10000 calls, and the > rest 1,750 being words to output 10,000 of code does not entice me > to use virtual calls. I understand that you say that, but I can't bring myself

I'm running Icecast 2.2.0 on RedHat Fedora core 2. It's working fine if I use the default port of 8000. I need to use port 80 because of client firewall issues. However when I try to reconfigure icecast.xml to port 80, I get "cannot create listener socket on port 80". I'm guessing it's some permissions issue in Fedora, but I'll be darned if I can find it! Any

Hi, I need to compile Icecast on a kind of ancient AIX machine. I compiled all the required libraries, except libvorbis, and I can't make it compile at all. Is there a way to compile Icecast without Ogg Vorbis support? Thanks! -- Regards, Alek Andreev alek@zvuk.net

...ook at http://samba.anu.edu.au/cvs.html Please note that these releases are not production quality. They may not even compile. That doesn't mean we don't want you to try them (we do!) it just means that if it doesn't work then you are honour bound to tell us what is wrong and not to be _too_ upset. Also note that the docs are a mess. If you want to know about an option or parameter then the source code is the only true guide. Hopefully the docs will improve over the coming weeks. If you are wondering "is there much difference between 1.9.18 and 2.0?" then the answer is a d...

I'm new to the list so please excuse me if this has already been rehashed before. There seems to be something very odd about how the PP_INSTANCE::PrevFragments array is handled during keyframes. I'm not a video codec expert so I'm not entirely sure what the reason for keeping a history of blocks updated in the last few previous interframes and adding them to the blocks to be

...ou have some sort of funkiness in your hardware. One unsubstantiated theory is that the vdec clock is *disabled*, and pcrypt is hooked up to that clock. Or perhaps that clock is somehow broken. It'd be interesting to see whether the old blob version can be made to work, but I wouldn't spend _too_ much time on it. May be easy to do with an older livecd or something. So, in order to completely disable PCRYPT without patching your system you can boot with "nouveau.config=PCRYPT=0" in your kernel cmdline (since 3.7, I think). It will also disallow userspace from using PCRYPT, which i...

...t version of >> gcc llvm is based on(and it's still available). > > > I have already opened a "wishlist" bug to merge llvm-gcc with current > gcc 3.4 CVS branch - http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=498 . > > Actually I don't think it would be _too_ much work, but it requires > intimate knowledge of the llvm internals (and a good merge tool), so > this is probably outside the scope of an external contributor. > by "check this myself" I was talking about checking, if this is a gcc or a llvm bug by compiling and testing t...

...ice). Can anyone help me with these requirements? My best attempt is below, but it is no good because the ylab argument that I'm trying to use for the row labelling gets clipped. Also, I can't get my horizontal spacing to be equal to my vertical spacing (although the code below isn't _too_ bad). f <- function(...){ jj <- expand.grid(1:10,1:10) colnames(jj) <- c("","") par(mai=rep(0,4)+0.2) plot(jj,pch=16,asp=1, axes=FALSE, ...) } postscript(file="~/f.ps",width=5,height=7) par(mfrow=c(4,3)) f(main="t=1",ylab="fis...

...e for the Debian >>>> package for LLVM, including the C/C++ front end. I'm running >>>> this build on LLVM 1.4 source (the released tarball), using >>>> Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64 >>>> box, dual CPU). Before I get _too_ deep into it, I thought I >>>> would ask if the following compilation failure on the CFE >>>> looks the least bit familiar to anyone: >>>> >>>> >>>> /home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/xgcc >>>> -B/home/ahs3/llvm/llv...

...of funkiness in your hardware. One unsubstantiated theory is that the > vdec clock is *disabled*, and pcrypt is hooked up to that clock. Or perhaps > that clock is somehow broken. It'd be interesting to see whether the old blob > version can be made to work, but I wouldn't spend _too_ much time on it. May > be easy to do with an older livecd or something. I could try and do an install of RHEL6.2 (before the ABI change) onto an USB HDD. On this version, 285.09 still ran fine. What exactly would you want me to check with the "blob"? Is there any diagnostic tool tha...

...g to build everything from source for the Debian >> package for LLVM, including the C/C++ front end. I'm running >> this build on LLVM 1.4 source (the released tarball), using >> Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64 >> box, dual CPU). Before I get _too_ deep into it, I thought I >> would ask if the following compilation failure on the CFE >> looks the least bit familiar to anyone: >> >> >> /home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/xgcc >> -B/home/ahs3/llvm/llvm-1.4/cfrontend/build/gcc/ >> -B/usr/lib/llv...

...allel. It's also impossible to use multiple engines on the same channel like this on MSDEC4 (VP5) GPUs, so the same separate channel usage that you need to have for MSDEC4 should also be used for everything down to G84. First off, thank you so much for diving into our code! Hope it wasn't _too_ dirty :) Yeah, for Kepler, we put things on separate channels. When I did the VP2 implementation, I also put them on separate channels since it seemed like that was what was being done from the traces (and I knew much less about all these things back then). But when I was doing the initial pass to...