search for: gasiuna

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 running da...

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 l...

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....

...#39;re also interested in increasing the general stability of the whole llvm w.r.t. error situations. Best regards, Philipp -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Philip Reames Sent: Freitag, 13. Dezember 2013 02:04 To: Gasiunas, Vaidas; LLVM Dev Subject: Re: [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...

...tability of the whole llvm > w.r.t. error situations. > > Best regards, > Philipp > > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu > [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Philip Reames > Sent: Freitag, 13. Dezember 2013 02:04 > To: Gasiunas, Vaidas; LLVM Dev > Subject: Re: [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 do...

...nk? Yes, we would be glad to contribute our patches. I have to retest everything on trunk, because until now we used only the official LLVM3.3 release. Regards, Vaidas -----Original Message----- From: Kaylor, Andrew [mailto:andrew.kaylor at intel.com] Sent: Freitag, 20. Dezember 2013 18:41 To: Gasiunas, Vaidas; Philip Reames; LLVM Dev Subject: RE: [LLVMdev] Making LLVM safer in out-of-memory situations Hi Vaidas, 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 receiv...

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

>> 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

...tability of the whole llvm > w.r.t. error situations. > > Best regards, > Philipp > > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu > [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Philip Reames > Sent: Freitag, 13. Dezember 2013 02:04 > To: Gasiunas, Vaidas; LLVM Dev > Subject: Re: [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 do...

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.