search for: reasonnably

Hi, I have the following config; 4 ices hosts, ices-kh60 2 are streaming to icecast2.1kh5 server. 2 are streaming to icecast2.2kh9 server. The 2 hosts streaming to icecast2.2kh9 are crashing (machine crash...) twice a week. I was thinking of hardware problem, but it think it's not the case. To feed ices, I use: rawrec | ices Which I found very sensitive and may cause machine handup if

Thanks Eli, After digging thru mail archives & bugzilla, it seems fixing properly this issue would require a major change in the selectionDAG code --- to have it operate on a per function basis 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

...n on patches A and B. I intended to use the replicated goodness-of-fit test (G-statistic) described in Sokal & Rohlf (1981): this test seemed accurate for such data... But a first problem is that some frequencies in my data set are = 0... I wonder if an x->( x + 1) transformation could be reasonnably performed to permit the taking of ln(X) in calculations. Moreover, low frequencies (less than 5) are usually reported as a problem for G-tests, and because my females had only the choice to oviposit on 6 patches (3 for treatment A, 3 for treatment B), I have indeed low frequencies! Do you know...

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

...mportant to insist on this, in a world populated with a myriad of slowly developed, half finished, half featured R GUIs, made by people that look too individualist in my view to be able of working all together and to write a single R GUI that has any chance to be full-featured, well-documented, reasonnably bug-free, truly platform-independent, in a near future. Best, Philippe Grosjean ..............................................<?}))><........ ) ) ) ) ) ( ( ( ( ( Prof. Philippe Grosjean ) ) ) ) ) ( ( ( ( ( Numerical Ecology of Aquatic Systems ) ) ) ) ) Mons-Hainaut Univer...

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

...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 (python2/python3/ruby/javascript/perl/guile...) It is to keep the technical cost the lowest possible in order to let the door reasonnably open to alternatives of the same language. c++ is slapping this door at the face of any attempt to produce working alternatives. An other point of view is the level of entry which is usually much higher on c++ projects due to syntax complexity, and often non-pertinent in the goal to achieve. Then...

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