search for: situation

...e to native code, primarily on x86-64 platforms. Our programs are created dynamically, compiled and optimized in a running database. As a result of that we have special requirements with respect to response time and safety. In particular, we have to avoid long compile times and must deal with error situations like out-of-memory without crashing or producing memory leaks in the compiler. The compiler performance is especially important since that we must compile generated functions which tend to be rather long - in the range of thousands of LOC per function. To address these requirements we have devel...

...m: "Philipp Becker" <philipp.becker at sap.com> > To: "Philip Reames" <listmail at philipreames.com>, "LLVM Dev" <llvmdev at cs.uiuc.edu> > Sent: Friday, December 13, 2013 6:55:59 AM > Subject: Re: [LLVMdev] Making LLVM safer in out-of-memory situations > > Hi Philip, > > Thanks for the positive response from all of you! > > > One question: How are you handling EOM? Error return? Custom > > region allocator? > > When running into an Out-of-memory situation we're currently only > doing an error return...

Hi Philip, Thanks for the positive response from all of you! > One question: How are you handling EOM? Error return? Custom region allocator? When running into an Out-of-memory situation we're currently only doing an error return, i.e. the compilation fails, but does so without crashing the process in which the compilation/jitting occurs. It is ok for us if llvm returns with a catchable exception and unwinds all allocated memory correctly. To increase stability for us we have...

...e to native code, primarily on x86-64 platforms. Our programs are created dynamically, compiled and optimized in a running database. As a result of that we have special requirements with respect to response time and safety. In particular, we have to avoid long compile times and must deal with error situations like out-of-memory without crashing or producing memory leaks in the compiler. The compiler performance is especially important since that we must compile generated functions which tend to be rather long - in the range of thousands of LOC per function. > > To address these requirements we ha...

...ity, But let's assume that this is the issue, there is no reason that 30 listeners >From the same country will connect and disconnect at the same time range... I'm pretty sure that its individual listener/IP. I deleted the Access log files, but in the next time that I will catch similar situation again, I will complete the investigation. Nobody from you folks get into situation like mine before? -----Original Message----- From: Icecast-dev [mailto:icecast-dev-bounces at xiph.org] On Behalf Of Christoph Zimmermann Sent: Saturday, July 02, 2016 12:32 AM To: icecast-dev at xiph.org Subjec...

Hi all, I've recently been writing functions which may deal with very large arrays. And I hope to use *apply functions in the program so that the code may look nicer and the performance may be better in the following two situations. The first situation is: I'm having an array A with dim(A)==c(m,n,p). And I want to apply a function F to a group of elements in A like: 1) F is applied to every group of elements like A[i,j,] for all i and j. or 2) F is applied to every group of elements like A[i,,] for all i, or A[,j,] fo...

...ire much effort. > Does this mean that you're compiling your build of LLVM with exceptions > enabled? By default, I believe LLVM is built without RTTI or exception > support. OK, I see. This explains why the destructors in LLVM are not always prepared to be executed in exception situations. Yes, we build LLVM with exception support. In principle, we build it with the same options like the rest of our project. Actually, I could hardly imagine that we could handle OOM situations without error handling. > For the particular cases you mentioned with auto pointers and allocation...

...oid memory allocation in destructors in the first place. Best regards, Philipp -----Original Message----- From: Hal Finkel [mailto:hfinkel at anl.gov] Sent: Freitag, 13. Dezember 2013 14:32 To: Becker, Philipp Cc: Philip Reames; LLVM Dev Subject: Re: [LLVMdev] Making LLVM safer in out-of-memory situations ----- Original Message ----- > From: "Philipp Becker" <philipp.becker at sap.com> > To: "Philip Reames" <listmail at philipreames.com>, "LLVM Dev" <llvmdev at cs.uiuc.edu> > Sent: Friday, December 13, 2013 6:55:59 AM > Subject: Re: [LLVM...

...ave developed a set of patches improving performance and malfunction safety of certain compiler passes and would be interested in contributing them at some point. Before proposing concrete changes, we would like to know what the general interest is with respect to making LLVM safer in out-of-memory situations. I'm in favor! I can't imagine we shouldn't be able to craft fixes that don't otherwise adversely affect LLVM. -- Rick -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 204 bytes Desc: Mess...

...a catchment's outlet. Some guys have shown that if there is a significant fit to a linear model, one can deduce the dynamic state of the basin, that is, whether erosion is as strong as rock uplift, erosion is smaller than rock uplift, or erosion is greater than rock uplift. I am thus to test 4 situations: Situation 1: a linear model is inappropriate for describing the data, the scatter is too large, and thus a linear model is unfit to explain the data. Situation 2: the linear model of the kind "y = b0 + b1 * x" is fit to describe the data, ie data points lie close to a straight line....

...About players, I can't control what the "radio index" sites are doing with my icecast streaming address, But as far as I know from my experience, the players when they getting "crazy" causing between 3-5 multiple connections for less than a 2 minutes. Not a big issue. The situation that I'm describing is very different, 20-30 (and once even almost 40) "listeners" from the same IP, for a long time. Each "listener" using true bandwidth. The IP source is from Vietnam, Korea...i really think that abusing its what I'm talking about. ( What a mobile dev...

...et=10.0.0.0/255.0.0.0 localnet=172.16.0.0/12 nat=yes --------------------------------------------------------------------------- in [general] section of sip.conf. I can make perfect conversation with my friend with the only exception of both parties being on private ip address. There can be four situations when a call is established. 1. A and B are not behind NATs 2. A is behind a NAT, but B is not. 3. A is not behind a NAT, but B is. 4. A and B are both behind NATs (different NAT of course). Among the four situations, 1, 2 and 3 works fine. (I guess externhost and localnet did the trick) But situa...

Hi everyone, The MachineLICM pass has a heuristic such that, even in low-register-pressure situations, it will refuse to hoist "cheap" instructions out of loops. By default, when an itinerary is available, this means that all of the defined operands are available in at most 1 cycle. ARM overrides this, and provides this more-customized definition: bool ARMBaseInstrInfo:: hasLowDefLatenc...

Hi everybody. I'm in a discussion and someone ask me in which situation we should use the zapata.conf usecallerid set to no. I didn't have the answer. I understand what the usecallerid keyword does but I'm talking about a actual situation that is interesting to to avoid receiving the caller id. Thanks in advance! -- -----------------------------------------...

I have some specs that involve the use of eval and class definitions to test code generation. I want to always start with a clean slate so none of my tests fail or succeed incorrectly due to artifacts left over from previous specs. Example of my situation Spec 1 defines class Fish class Cod < Fish Spec 2 defines class Animal class Cod < Animal In this situation the second spec will fail since Cod was previously defined to be a subclass of Fish and you can not change the superclass of a subclass in ruby without causing an...

...2.4.31 There is share on the server (for DBASE app) with following config: comment = zwierzaki 2.5.04N path = /pub/zwierz/ force user = smbguest read only = No guest only = Yes guest ok = Yes dos filetime resolution = Yes I have found weird situation: - not every file in shared dir is visible under windows but all files are visable under unix - file created under linux is not visable under windows - file created under windows is not visable under linux I know it sounds weird, like DBASE shouldn work... but it does. I will try to restart server...

...vm-dev wrote: >> What should be used for type declarations: typedef or using? typedef >> is there because of historical reasons, but LLVM code based is C++11 >> now. >> >> LLVM Coding Standards are not clear on this matter. > > Can you give some context for the situation you wonder about? They are > both valid in some situation. Are there cases were typedef is (technically) preferable (or needed) compared to using? — Mehdi

...oving Eaton from the "Main supporter" to "Supporting UPS manufacturer", rewording the content and putting a big warning [1]. Quoting these main changes: "Eaton, has been the main NUT supporter in the past, between 2007 and 2011, continuing MGE UPS SYSTEMS efforts. ... The situation has evolved, and since 2011 Eaton does not support NUT anymore. This may still evolve in the future. But for now, please do not consider anymore that buying Eaton products will provide you with official support from Eaton, or a better level of device support in NUT." Considering that I'm...

If anyone is running this configuration, I have some questions for you about Page83 data errors. This message posted from opensolaris.org

On 12/13/13 6:47 AM, Becker, Philipp wrote: > Hi Hal, > >> Does this mean that you're using C++ exception handling to manage the cleanup? > No, not really. From the place where we're calling into llvm we are catching all exceptions that may occur during compilation, but normally we do not add any additional catch clauses into the llvm source itself. We mainly rely on correct