similar to: [LLVMdev] Making LLVM safer in out-of-memory situations

On 12/12/13 4:25 AM, Gasiunas, Vaidas wrote: > Hello, > > Philipp Becker and me, Vaidas Gasiunas, are developers at SAP and part of a team developing a C-like domain-specific language for the SAP HANA in-memory database. We use LLVM as a backend to translate our language to native code, primarily on x86-64 platforms. Our programs are created dynamically, compiled and optimized in a

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

----- 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: [LLVMdev] Making LLVM safer in out-of-memory situations > > Hi Philip, > > Thanks for the

On Dec 12, 2013, at 04:25 , Gasiunas, Vaidas <vaidas.gasiunas at sap.com> wrote: > To address these requirements we have 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

Hi Andy, > I would think you could use a simple allocation scheme on the host side and then allocate a single block (or perhaps one code block and one data block) in the target process to receive everything, since everything is loaded on the host before you need to copy it to the target process. But perhaps I'm missing something regarding your particular scenario. > In any event,

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 stack unwinding by destructors in llvm when an exception is

>> To increase stability for us we have already moved the main part of the compilation to a separate process that may crash in case of an error without doing much harm, i.e. does not crash the database. > Were there any interesting challenges that arose during this process? > This seems to be an approach many folks are either taking or > considering. If there are things we could

Hi Philip, > If I'm reading you correctly, you are relying on exception propagation > and handler (destructors for local objects) execution. You have chosen > not to add extra exception logic to LLVM itself, but are relying on the > correctness of exception propagation within the code. (The last two > sentances are intended to be a restatement of what your message said.

Some time ago we reported a compile-time performance regression in the LiveIntervals analysis pass (see http://llvm.org/bugs/show_bug.cgi?id=18580). We detected it at first after migrating from LLVM 3.1 to 3.3, but the problem persists also in 3.5. This regression is especially critical when compiling long functions. In one of our benchmarks compile time goes from 200s (in 3.1) up to 1500s (in

On 12/13/13 4:55 AM, Becker, Philipp wrote: > To increase stability for us we have already moved the main part of the compilation to a separate process that may crash in case of an error without doing much harm, i.e. does not crash the database. Were there any interesting challenges that arose during this process? This seems to be an approach many folks are either taking or considering. If

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

Hi, all I ported llvm backend and lldb recently. Both tools can basically work. lldb is able to debug programs in asm style and frame unwinding is OK. But "frame variable XX" does not work because lldb is not able to determine the address of XX from debug info. Can someone give any clue? Thanks in advance. -- 杨勇勇 (Yang Yong-Yong) -------------- next part -------------- An HTML

Hi! I have a matrix called M with dimension (586,100,100). I would like to split and save this into 586 matrices with dimension 100 by 100. I have tried the following for loops but couldn't get it work.. l<-dim(M)[1] for (i in (1:l)){ save(M[i,,],file = "M_[i].img") } Can somebody help me with this? Thanks! Hana Lee [[alternative HTML version deleted]]

Sorry, this is the attachment. 2014-02-19 15:08 GMT+08:00 杨勇勇 <triple.yang at gmail.com>: > Thank you. > > Here is an example and the attchment contains extra files including object > file and executable file. > I want to print for example the value of "a", but lldb command "frame > variable a" displays "0" and so does "b", and

All of this information is contained in the DWARF debug info that you must generate. Are you generating DWARF? If not, you will need to. If so, please attach an example program that contains DWARF and specify which function you are having trouble getting variable information for. Greg Clayton On Feb 18, 2014, at 12:44 AM, 杨勇勇 <triple.yang at gmail.com> wrote: > Hi, all > > I

On Mon, Jun 20, 2016 at 10:01 AM, Anton Korobeynikov via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > P.S.: On a similar note, are there any news regarding llvm.org/apt? > We are working on it. Note, however, that it seems that the majority > of bogus load seemed to come from CI systems, which pulled apt repo > for every and each downstream commit without any caching /

> -----Original Message----- > From: Richard A. O'Keefe [mailto:ok at cs.otago.ac.nz] <snip> > The very existence of an "is.na<-" which accepts a logical > vector containing FALSE as well as TRUE ... And don't forget this is not the only usage of is.na<-. In fact it is designed to take any valid indexing value. For example: > a<-1:10 >

Hi People, I have a quick question, which hopefully you will have an answer to. I am slowly moving towards puppet and git with multiple branches for different environments. Things are going pretty well, but now I have a small issue. The question is where should I store sensitive files, for instance SSL private keys or some files which contain sensitive data? I am aware of hiera-gpg storage

Dear lists, It seems that RODBC has a problem : when reading through ODBC from an Access table with missing values, *character* missing values are (correctly) reported as NA factor values. *Numeric* values, however, retain the value of the same variable in the previous row. My setup : R 1.1.1 under Win95, RODBC as compiled with the R Win CRAN distribution, MS Access 97. I just discovered this,

Dear lists, It seems that RODBC has a problem : when reading through ODBC from an Access table with missing values, *character* missing values are (correctly) reported as NA factor values. *Numeric* values, however, retain the value of the same variable in the previous row. My setup : R 1.1.1 under Win95, RODBC as compiled with the R Win CRAN distribution, MS Access 97. I just discovered this,