From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Error handling in sparse-llvm
Date: Mon, 13 Mar 2017 11:00:24 +0000 [thread overview]
Message-ID: <CACXZuxfOgu_LbgG1iT8S2nYz5CAr181zOaM7jivsYKA4hO1vqg@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxeKQgPZWd-AQkzQnMMH0EyQOuinzUTXL9qkWYk3pbi6XA@mail.gmail.com>
On 13 March 2017 at 10:43, Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
> On 12 March 2017 at 19:53, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
>> On Sun, Mar 12, 2017 at 07:40:18PM +0000, Dibyendu Majumdar wrote:
>>> At present there are a bunch of asserts for scenarios not handled by
>>> Sparse LLVM backend. A more robust error handling method is needed
>>> that works even in release builds, and doesn't abort the process.
>>> Given the way the code is structured currently, I was thinking maybe
>>> it will be easiest to use setjmp/longjmp mechanism to terminate the
>>> LLVM backend on error. I am not sure that this entirely safe with LLVM
>>> as the LLVM code is C++ - I think it might be okay as long as the LLVM
>>> module / context is properly disposed at the end.
>>
>> By far, the best thing that can be done is to add support for the missing
>> features/scenarios so that those asserts can be removed.
>>
>
> Agreed, but that will probably take some time. In the meantime even
> with the subset supported by Sparse-LLVM it can be used in
> applications - provided it deals with supported features gracefully
> and generates correct code for supported features.
>
Apologies for the typo - I meant to say 'it deals with unsupported
features gracefully'.
Regards
prev parent reply other threads:[~2017-03-13 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 19:40 Error handling in sparse-llvm Dibyendu Majumdar
2017-03-12 19:53 ` Luc Van Oostenryck
2017-03-13 10:43 ` Dibyendu Majumdar
2017-03-13 11:00 ` Dibyendu Majumdar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACXZuxfOgu_LbgG1iT8S2nYz5CAr181zOaM7jivsYKA4hO1vqg@mail.gmail.com \
--to=mobile@majumdar.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.