caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Thomas Wies <wies@cs.nyu.edu>
To: caml-list@inria.fr
Subject: [Caml-list] TAPAS 2017: Call for Abstracts
Date: Tue, 6 Jun 2017 08:35:15 -0400	[thread overview]
Message-ID: <43c4d19a-cecc-b1ff-4b8f-3a93a65e3b8f@cs.nyu.edu> (raw)

                           Call for Abstracts
----------------------------------------------------------------------
          8th Workshop on Tools for Automatic Program Analysis

                               TAPAS 2017
----------------------------------------------------------------------

August 29, 2017
New York, NY, USA
A Satellite Workshop of SAS 2017

http://cs.nyu.edu/acsys/tapas2017/


Important Dates
---------------

   * Submission deadline:  June 26, 2017
   * Notification:         July 24, 2017
   * Workshop:             August 29, 2017


Objectives
----------

In recent years, a wide range of static analysis tools have emerged,
some of which are currently in industrial use or are well beyond the
advanced prototype level. Many impressive practical results have been
obtained, which allow complex properties to be proven or checked in a
fully or semi-automatic way, even in the context of complex software
developments. In parallel, the techniques to design and implement
static analysis tools have improved significantly, and much effort is
being put into engineering the tools. This workshop is intended to
promote discussions and exchange experience between specialists in all
areas of program analysis design and implementation and static
analysis tool users.

Scope
-----

The technical program of TAPAS 2017 will consist of invited lectures
together with presentations based on submitted extended abstracts.

Submissions can cover any aspect of program analysis tools including,
but not limited to the following:

   * design and implementation of static analysis tools (including
     practical techniques used for obtaining precision and performance);

   * components of static analysis tools (front-ends, abstract domains,
     etc.);

   * integration of static analyzers (in proof assistants, test
     generation tools, IDEs, etc.);

   * reusable software infrastructure (analysis algorithms and
     frameworks);

   * experience reports on the use of static analyzers (both research
     prototypes and industrial tools).


Submission
----------

Please visit the submission website:
<https://easychair.org/conferences/?conf=tapas2017>.

All submitted abstracts will be reviewed by the program committee.

Submitted abstracts should be up to 3 pages in the two-column
sub-format of the new ACM proceedings format.


Invited Speakers
----------------

Forthcoming.


Program Chair
-------------

   * Thomas Wies (NYU, USA)

Program Committee
-----------------

   * Michael Emmi (Nokia Bell Labs, USA)
   * Samir Genaim (UCM, Spain)
   * Arie Gurfinkel (University of Waterloo, Canada)
   * Laura Kovacs (TU Wien, Austria)
   * Isabella Maestroni (University of Verona, Italy)
   * Antoine Miné (UPMC University, France)
   * Damien Zufferey (MPI-SWS, Germany)

             reply	other threads:[~2017-06-06 12:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 12:35 Thomas Wies [this message]
2017-07-11 10:48 Thomas Wies

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=43c4d19a-cecc-b1ff-4b8f-3a93a65e3b8f@cs.nyu.edu \
    --to=wies@cs.nyu.edu \
    --cc=caml-list@inria.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).