Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Milovancevic, Dragana" <dragana.milovancevic@imperial.ac.uk>
To: "acl2@utlists.utexas.edu" <acl2@utlists.utexas.edu>,
	"all@cost-ic0701.org" <all@cost-ic0701.org>,
	"announce@informatics-europe.org"
	<announce@informatics-europe.org>,
	"caml-list@inria.fr" <caml-list@inria.fr>,
	"cl-isabelle-users@lists.cam.ac.uk"
	<cl-isabelle-users@lists.cam.ac.uk>,
	"coq-club@inria.fr" <coq-club@inria.fr>,
	"fm-announcements@lists.nasa.gov"
	<fm-announcements@lists.nasa.gov>,
	"events@fmeurope.org" <events@fmeurope.org>,
	"SREPLS@jiscmail.ac.uk" <SREPLS@jiscmail.ac.uk>,
	"theorem-provers@ai.mit.edu" <theorem-provers@ai.mit.edu>,
	"types-announce@lists.seas.upenn.edu"
	<types-announce@lists.seas.upenn.edu>,
	"verifythis-ltc@lists.kit.edu" <verifythis-ltc@lists.kit.edu>
Cc: Mattias Ulbrich <ulbrich@kit.edu>
Subject: [Caml-list] Call For Papers: 6th Workshop on Program Equivalence and Relational Reasoning (PERR2026 @ CAV/FLOC)
Date: Thu, 15 Jan 2026 14:09:37 +0000	[thread overview]
Message-ID: <LO2P265MB12300A3EE029C7BA1F32F8FFB58CA@LO2P265MB1230.GBRP265.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 3599 bytes --]

[with apologies for cross-postings]

======================================================================

       6th Workshop on Program Equivalence and Relational Reasoning
                24 July 2026 at ISCTE campus, Lisbon, Portugal
                  associated with CAV 2026 at FLOC 2026
                   https://perr-workshop.github.io/2026

======================================================================

Submission Deadline: Friday, 24 April, 2026 (AoE)

Submit at: https://submissions.floc26.org/perr

CALL FOR PAPERS/PRESENTATIONS

PERR is an annual international workshop dedicated to the formal verification of program equivalence and related relational problems. It is the 6th in a series of meetings that bring together researchers from different areas interested in equivalence and related questions. PERR 2026 will be a workshop at FLOC 2026, and a satellite event to CAV 2026.

Program equivalence is arguably one of the most interesting and at the same time important problems in formal verification. It is a cross-cutting topic that has attracted the interest of several research communities: the field of denotational (game) semantics, deductive software verification, bounded model checking, specification inference, software evolution and regression testing, etc.

The goal of the workshop is to bring researchers of the different fields in touch and to stimulate an exchange of ideas leading to forging a community working on PERR. It welcomes contributions from the topics mentioned above but is also open to new questions regarding program equivalence. This includes related research areas of relational reasoning like program refinement or the verification of hyperproperties, in particular of secure information flow.

      - regression verification
      - program equivalence
      - equivalence of higher order programs
      - product programs, relational calculi
      - verification of hyperproperties
      - program refinement, refinement calculus
      - specification of differences between programs
      - inferring semantic differences between programs
      - transformation validation
      - correct compiler transformations
      - automata bisimulation
      - AI-supported equivalence checking
      - relational properties of AI-based systems
      - code equivalence checking in teaching and marking

This is an informal workshop that welcomes work in progress, overviews of more extensive work, programmatic or position papers and tool presentations.

SUBMISSION GUIDELINES

We invite two types of submissions:

      - Regular papers. Regular papers should be at most 15 pages (excluding references). They should present original research results, tools, or case studies.

      - Extended Abstracts. Extended abstracts should be at most 3 pages (excluding references). They should introduce work that has recently been published or is under review, or work in progress.

Submissions should be made using the PERR 2026 submission site:

https://submissions.floc26.org/perr

Submissions must be a single PDF file, in LNCS format.

The workshop will have informal proceedings, posted on the webpage, and speakers will be asked to consider submitting papers towards a post-proceedings volume.

IMPORTANT DATES

    Submission Deadline: Friday, 24 April, 2026 (AoE)
    Notification: Thursday, 28 May, 2026
    Workshop: Friday, 24 July, 2026

ORGANIZERS

    Mattias Ubrich, Karlsruhe Institute of Technology, Germany
    Dragana Milovancevic, Imperial College London, UK

[-- Attachment #2: Type: text/html, Size: 19534 bytes --]

                 reply	other threads:[~2026-01-15 14:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=LO2P265MB12300A3EE029C7BA1F32F8FFB58CA@LO2P265MB1230.GBRP265.PROD.OUTLOOK.COM \
    --to=dragana.milovancevic@imperial.ac.uk \
    --cc=SREPLS@jiscmail.ac.uk \
    --cc=acl2@utlists.utexas.edu \
    --cc=all@cost-ic0701.org \
    --cc=announce@informatics-europe.org \
    --cc=caml-list@inria.fr \
    --cc=cl-isabelle-users@lists.cam.ac.uk \
    --cc=coq-club@inria.fr \
    --cc=events@fmeurope.org \
    --cc=fm-announcements@lists.nasa.gov \
    --cc=theorem-provers@ai.mit.edu \
    --cc=types-announce@lists.seas.upenn.edu \
    --cc=ulbrich@kit.edu \
    --cc=verifythis-ltc@lists.kit.edu \
    /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