What is the meaning of these constant interruptions?

Hutton, Graham; Wright, Joel

doi:10.1017/s0956796807006363

Cited by 13 publications

(12 citation statements)

References 39 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For brevity, we stay away from lambda-languages and binding issues, that with few exceptions [13,23,24] have been our favorite domain of discourse so far. Instead, we consider arithmetic expressions with effects (namely interruptions) and stuck terms (namely errors), as in Graham Hutton and Joel Wright's recent work [37]. In doing so, we aim at the same sort of telling, minimalistic elegance as can be found in Hutton's publications.…”

Section: Introductionmentioning

confidence: 99%

Defunctionalized interpreters for programming languages

Danvy

2008

Proceedings of the 13th ACM SIGPLAN International Conference on Functional Programming

View full text Add to dashboard Cite

This document illustrates how functional implementations of formal semantics (structural operational semantics, reduction semantics, small-step and big-step abstract machines, natural semantics, and denotational semantics) can be transformed into each other. These transformations were foreshadowed by Reynolds in "Definitional Interpreters for Higher-Order Programming Languages" for functional implementations of denotational semantics, natural semantics, and big-step abstract machines using closure conversion, CPS transformation, and defunctionalization. Over the last few years, the author and his students have further observed that functional implementations of small-step and of big-step abstract machines are related using fusion by fixed-point promotion and that functional implementations of reduction semantics and of smallstep abstract machines are related using refocusing and transition compression. It furthermore appears that functional implementations of structural operational semantics and of reduction semantics are related as well, also using CPS transformation and defunctionalization. This further relation provides an element of answer to Felleisen's conjecture that any structural operational semantics can be expressed as a reduction semantics: for deterministic languages, a reduction semantics is a structural operational semantics in continuation style, where the reduction context is a defunctionalized continuation. As the defunctionalized counterpart of the continuation of a one-step reduction function, a reduction context represents the rest of the reduction, just as an evaluation context represents the rest of the evaluation since it is the defunctionalized counterpart of the continuation of an evaluation function.

show abstract

Section: Introductionmentioning

confidence: 99%

Defunctionalized interpreters for programming languages

Danvy

2008

Proceedings of the 13th ACM SIGPLAN International Conference on Functional Programming

View full text Add to dashboard Cite

show abstract

“…We are not aware of previous operational semantics for signals, although Feng, Shao, Guo and Dong [6] presents a program logic for assembly language with interrupts, which are analogous to signals at the hardware level. Hutton and Wright [7] study interruptions as asynchronous exceptions. By contrast, signals are a software alternative to hardware interrupts, where signal handlers could be addressed as asynchronous subroutine calls.…”

Section: Discussionmentioning

confidence: 99%

Operational semantics for signal handling

Strygin¹,

Thielecke²

2012

Electron. Proc. Theor. Comput. Sci.

View full text Add to dashboard Cite

Signals are a lightweight form of interprocess communication in Unix. When a process receives a signal, the control flow is interrupted and a previously installed signal handler is run. Signal handling is reminiscent both of exception handling and concurrent interleaving of processes. In this paper, we investigate different approaches to formalizing signal handling in operational semantics, and compare them in a series of examples. We find the big-step style of operational semantics to be well suited to modelling signal handling. We integrate exception handling with our big-step semantics of signal handling, by adopting the exception convention as defined in the Definition of Standard ML. The semantics needs to capture the complex interactions between signal handling and exception handling

show abstract

“…Here and throughout this article, we use 'co' on the left of rules to indicate that the relation is coinductively defined by that set of rules. 5 We assume that the reader is familiar with the basics of coinduction (for introductions see, e.g., [3; 13; 14]).…”

Section: Infinite Computationsmentioning

confidence: 99%

“…Leroy and Grall [3] cite compiler correctness proofs as a main motivation for using coinductive big-step semantics as opposed to small-step semantics: using small-step semantics complicates the correctness proof. Indeed, Hutton and Wright [5] and Hutton and Bahr [40] also use big-step semantics for their compiler correctness proofs. However, in CompCert, Leroy [41] uses a small-step semantics and sophisticated notions of bisimulation for its compiler correctness proofs.…”

Section: Related Workmentioning

confidence: 99%

Flag-based big-step semantics

Poulsen

Mosses

2017

Journal of Logical and Algebraic Methods in Programming

View full text Add to dashboard Cite

Structural operational semantic specifications come in different styles: small-step and big-step. A problem with the big-step style is that specifying divergence and abrupt termination gives rise to annoying duplication. We present a novel approach to representing divergence and abrupt termination in big-step semantics using status flags. This avoids the duplication problem, and uses fewer rules and premises for representing divergence than previous approaches in the literature.

show abstract

What is the meaning of these constant interruptions?

Cited by 13 publications

References 39 publications

Defunctionalized interpreters for programming languages

Defunctionalized interpreters for programming languages

Operational semantics for signal handling

Flag-based big-step semantics

Contact Info

Product

Resources

About