All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Error handling in sparse-llvm
Date: Sun, 12 Mar 2017 19:40:18 +0000	[thread overview]
Message-ID: <CACXZuxcU4ZQ0=D67F4EkqyFKANQVjhSxfSzsqdzXbNXYsGXGfQ@mail.gmail.com> (raw)

Hi,

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.

Regards
Dibyendu

             reply	other threads:[~2017-03-12 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 19:40 Dibyendu Majumdar [this message]
2017-03-12 19:53 ` Error handling in sparse-llvm Luc Van Oostenryck
2017-03-13 10:43   ` Dibyendu Majumdar
2017-03-13 11:00     ` Dibyendu Majumdar

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='CACXZuxcU4ZQ0=D67F4EkqyFKANQVjhSxfSzsqdzXbNXYsGXGfQ@mail.gmail.com' \
    --to=mobile@majumdar.org.uk \
    --cc=linux-sparse@vger.kernel.org \
    /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.