formal/spinhint: Update code snippet
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | fcvextract.pl: Treat '.spin' files as C sourcesutilities/ | +2 | 0 replies | |
| 2/6 | formal/spinhint: Employ new scheme for code snippetCodeSamples/ CodeSamples/ CodeSamples/ +3 more | +318 | 0 replies | |
| 3/6 | formal/spinhint: Update output lists of spinCodeSamples/ CodeSamples/ CodeSamples/ +3 more | +140 | 0 replies | |
| 4/6 | formal/spinhint: Update tables of memory usage of Spinformal/ | +39 | 0 replies | |
| 5/6 | formal/spinhint: Put footnote on header in tableformal/ perfbook.tex | +7 | 0 replies | |
| 6/6 | formal/spinhint: Use \co{...} rather than {\tt ...}formal/ | +7 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] formal/spinhint: Update code snippet
Hi Paul,
Here is another round of code snippet update, with modernization of outputs of Spin and tables of state search results.
Patch #1 updates fcvextract.pl so that .spin files are handled as the same as C source files.
Patch #2 applies the new scheme to code snippets. It also contains minor changes for better typesetting.
Patch #3 replaces captures of Spin outputs with those obtained from Spin version 6.4.8. This commit adds outputs as .lst files under CodeSamples/formal/promela/. They are added to the dependency in the top level Makefile.
Patch #4 updates tables of Spin result. For qrcu.spin, I used the compiler flag -DCOLLAPSE to complete the state search for updaters=3 readers=2 on a machine with 16GB memory. As far as I understand correctly, this compiler flag does not affect the completeness of state search. So I added some explanation in the text to mention the flag and the argument -mN of ./pan to increase the limit of search depth.
Patch #5 tweaks footnote on a cell in a table.
Patch #6 is a nitpick patch to consistently use \co{}.
I'm wondering if Patch #4 is OK from your perspective. Any feedback is welcome!
Thanks, Akira
--
Akira Yokosawa (6):
fcvextract.pl: Treat '.spin' files as C sources formal/spinhint: Employ new scheme for code snippet formal/spinhint: Update output lists of spin formal/spinhint: Update tables of memory usage of Spin formal/spinhint: Put footnote on header in table formal/spinhint: Use \co{...} rather than {\tt ...}
CodeSamples/formal/promela/atomicincrement.spin | 2 + .../formal/promela/atomicincrement.spin.lst | 28 + CodeSamples/formal/promela/increment.spin | 46 +- CodeSamples/formal/promela/increment.spin.lst | 28 + .../formal/promela/increment.spin.trail.lst | 42 + CodeSamples/formal/promela/lock.h | 16 +- CodeSamples/formal/promela/lock.spin | 46 +- CodeSamples/formal/promela/lock.spin.lst | 29 + CodeSamples/formal/promela/qrcu.spin | 95 ++- Makefile | 4 +- formal/spinhint.tex | 874 ++++++--------------- perfbook.tex | 1 + utilities/fcvextract.pl | 8 +- 13 files changed, 502 insertions(+), 717 deletions(-) create mode 100644 CodeSamples/formal/promela/atomicincrement.spin.lst create mode 100644 CodeSamples/formal/promela/increment.spin.lst create mode 100644 CodeSamples/formal/promela/increment.spin.trail.lst create mode 100644 CodeSamples/formal/promela/lock.spin.lst
Signature · 1 line
2.7.4