MAJ terminée. Nous sommes passés en version 14.6.2 . Pour consulter les "releases notes" associées c'est ici :

https://about.gitlab.com/releases/2022/01/11/security-release-gitlab-14-6-2-released/
https://about.gitlab.com/releases/2022/01/04/gitlab-14-6-1-released/

Commit e38cd3a4 authored by POTTIER Francois's avatar POTTIER Francois
Browse files

Comments.

parent 8c9718e2
......@@ -111,7 +111,6 @@
\newcommand{\iif}[3]{\kw{if}\,\deref#1\,\kw{then}\,#2\,\kw{else}\,#3}
\newcommand{\icall}[2]{\deref#1(#2)}
\newcommand{\ialloc}[2]{\deref#1 \assign \kw{alloc}\;#2}
% LATER use \deref(...) instead of square brackets in load and store?
\newcommand{\iload}[3]{\deref#1 \assign [\deref#2+#3]}
\newcommand{\istore}[3]{[\deref#1+#2] \assign \deref#3}
\newcommand{\iloceq}[3]{\deref#1 \assign (\deref#2 == \deref#3)}
......@@ -242,7 +241,6 @@
\newcommand{\ZeroDag}{Zero$\ddag{}$}
\newcommand{\JoinDag}{Join$\ddag{}$}
% LATER decide where/whether to use this
\newcommand{\mathsmash}[1]{\ensuremath{\smash{#1}}}
% ------------------------------------------------------------------------------
......
\section{Related Work}
\label{sec:related}
% TODO note that a bound on the size of the live data
% does not imply a bound on the size of the heap;
% if one wishes to prove that the program can run in a heap of size N
% without failure, then this depends on a concrete GC; cite Hobor?
% LATER note that a bound on the size of the live data
% does not imply a bound on the size of the heap;
% if one wishes to prove that the program can run in a heap of size N
% without failure, then this depends on a concrete GC; cite Hobor?
% https://www.comp.nus.edu.sg/~hobor/Publications/2019/Localize.pdf
There is a rich literature on measuring or controlling the heap space
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment