Displaying 8 results from an estimated 8 matches for "codeloader".
2013 Dec 13
4
[LLVMdev] Making LLVM safer in out-of-memory situations
...ty 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. Therefore, we've currently concentrating on specific components that still remain in the database process, such as CodeLoader and VMCore, which is used for emitting IR code. Although, of course, we'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.ed...
2013 Dec 19
0
[LLVMdev] Making LLVM safer in out-of-memory situations
...his process?
This seems to be an approach many folks are either taking or
considering. If there are things we could do to make this easier, it
might be worth considering.
> Therefore, we've currently concentrating on specific components that still remain in the database process, such as CodeLoader and VMCore, which is used for emitting IR code. Although, of course, we're also interested in increasing the general stability of the whole llvm w.r.t. error situations.
>
Understood. If you have patches that need reviewed, I'd be happy to help.
Philip
2013 Dec 20
3
[LLVMdev] Making LLVM safer in out-of-memory situations
...his process?
This seems to be an approach many folks are either taking or
considering. If there are things we could do to make this easier, it
might be worth considering.
> Therefore, we've currently concentrating on specific components that still remain in the database process, such as CodeLoader and VMCore, which is used for emitting IR code. Although, of course, we're also interested in increasing the general stability of the whole llvm w.r.t. error situations.
>
Understood. If you have patches that need reviewed, I'd be happy to help.
Philip
_________________________________...
2013 Dec 13
0
[LLVMdev] Making LLVM safer in out-of-memory situations
...ready 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.
> Therefore, we've currently concentrating on specific components that
> still remain in the database process, such as CodeLoader and VMCore,
> which is used for emitting IR code. Although, of course, we'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.u...
2013 Dec 13
0
[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
2014 Jan 03
2
[LLVMdev] Making LLVM safer in out-of-memory situations
...this process?
This seems to be an approach many folks are either taking or considering. If there are things we could do to make this easier, it might be worth considering.
> Therefore, we've currently concentrating on specific components that still remain in the database process, such as CodeLoader and VMCore, which is used for emitting IR code. Although, of course, we're also interested in increasing the general stability of the whole llvm w.r.t. error situations.
>
Understood. If you have patches that need reviewed, I'd be happy to help.
Philip
_________________________________...
2013 Dec 13
2
[LLVMdev] Making LLVM safer in out-of-memory situations
...ready 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.
> Therefore, we've currently concentrating on specific components that
> still remain in the database process, such as CodeLoader and VMCore,
> which is used for emitting IR code. Although, of course, we'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.u...
2013 Dec 12
7
[LLVMdev] Making LLVM safer in out-of-memory situations
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 database. As a result of that we have special