search for: reasonnable

...ery sensitive and may cause machine handup if any trouble. Is it possible that under certain circumstances, icecast2.2kh9 is blocking something, causing ices freeze, then rawrec crashing the machine while trying to do access sound card without being able to send audio to ices ? This is the only reasonnable explanation to the problem I found. What other solution may I use to read sound card input rather than using rawrec ? I saw in icecast2.2kh12e that there is some socket changes. Can this may correct the above problem? (I will take several days to test for me) Best regards, Chris

...s instead of per basic-block. This however, does not seem to be the only issue. The following C code does not produce an efficicient assembly sequence either. extern void f(unsigned long long v); void test2() { for (unsigned i=0; i<512; i++) f(i); } The resulting .ll out of clang looks reasonnable (with and without the patch), but the arm assembly output looks ugly, though marginally better with my patch : the induction variable should be counting up, and it could be zero extended before the call to f. This again points to Isel, but to a different area, as everything is taking place in the s...

Dear all, I am facing a problem that seems to me more tricky now that it did at first sight. I have a collection of data which consist in frequency distributions: 6 patches had been proposed to female insects (for oviposition), 3 of them corresponding to one treatment (A), the other 3 to another treatment (B). The results are the number of patches that have been chosen for oviposition by

Hi, I'm using Samba quiet a while and never had a problem I couldn't solve for myself. Now I've got one :) Everytime I write files > 30 MB on my exported Fujitsu M2513A Windows is terminating with "Network share is no longer available". The Windows progress indicator shows nothing, but the file is written and then discarded (after the error message) ! Now I've set the

Hi Oskar, > If having two build systems is a problem, just standardize on cmake. Does cmake support cross-compilation? Can it cross-compile LLVM ? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hello, Just a quick message to correct what I have said in my previous post.It finally seems not that easy to code small wavelet coefficients to have a good precision, and SPIHT is certainly a very good algorithm for that, -and I know there are SPIHT experts that can make very good SPIHT-based codecs-.I have chosen a new and different approach, the multistage residual coding, so I will try to

On Mon, Oct 17, 2016 at 1:41 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 17 October 2016 at 19:44, Daniel Berlin <dberlin at dberlin.org> wrote: > > First stage of gcc is the entire compiler, not a subset or a different > > compoiler. > > I didn't mean a different compiler, just not a full "toolchain". > Ah. You said "GCC has a

On 5/18/20 8:24 PM, Craig Topper wrote: > I can tell you that your avx512 issue is that v64i8 gfni instructions also > require avx512bw to be enabled to make v64i8 a supported type. The C > intrinsics handling in the front end know this rule. But since you > generated your own intrinsics you bypassed that. Indeed that's the issue... I was stick with what Intel announces here

Hello, Following a discussion initiated on r-devel, that mentions SciViews-R and other GUIs issues for R, I would like to make comments (and would be happy if these comments would initiate interesting initiatives). A big, big problem with SciViews-R is that a part of it is written in Visual Basic 6, a M$$$$ language, not supported any more, buggy, non transposable to other platforms, etc,

On Sun, Mar 13, 2011 at 5:01 PM, Arnaud Allard de Grandmaison <Arnaud.AllardDeGrandMaison at dibcom.com> wrote: > Hi all, > > The IndVarSimplify pass seems to be too aggressive when it enlarge the induction variable type ; this can pessimize the generated code when the new induction variable size is not natively supported by the target. This is probably not an issue for x86_64,

Hello, Alain. > I'm starting to play with LLVM today and I've trouble compiling it. > I'm > working under Windows Vista, with the gcc from Cygwin: Oh, this seems to be killer mix :) GCC (at least native mingw32 port) has known problems being running on Vista. > Is LLVM supposed to work with this version of GCC (probably using the > -mno-cygwin option to get a

Hi, This is not the purpose of my distro. The purpose of my distro is to account for complexity lock-in and to remove this as much as possible. This complexity is usually performed in 2 ways: - ultra costly languages/runtime to implement (c++/java...), and I don't think "ultra" is a word big enough. - multiplication of script languages

Hi all, The IndVarSimplify pass seems to be too aggressive when it enlarge the induction variable type ; this can pessimize the generated code when the new induction variable size is not natively supported by the target. This is probably not an issue for x86_64, which supports natively all types, but it is a real one for several embedded targets, with very few native types. I attached a patch to

Hi folks, I''m having (as the title suggests) a problem with zfs send/receive. Command line is like this : pfexec zfs send -Rp tank/tsm@snapshot | ssh remotehost pfexec zfs recv -v -F -d tank This works like a charm as long as the snapshot is small enough. When it gets too big (meaning somewhere between 17G and 900G), I get ssh errors (can''t read from remote host). I tried

Let''s move this to the Shorewall Development list.... On Tuesday 10 February 2004 03:14 pm, xavier wrote: > here is a patch to allow this : > |ACCEPT<10/sec:20>:debug fw lan:$ntp_servers udp 123 - - - - ntp > > a problem with the patch is that now the logprefix is mandatory. > i''m trying to debug it, but i can''t find the flaw. Also, with