line ending, date and margin fixes

Author: matu3ba

assets/style.css

@@ -31,6 +31,7 @@
 
   --content_width: 1200px; /* same as @media screen */
   --content_1colof2_width: calc(var(--content_width) / 2);
+  --list_item_margin_top: 4px;
 }
 
 body {
@@ -43,6 +44,7 @@ h1 { font-size: var(--font_size_h1); }
 h2 { font-size: var(--font_size_h2); }
 h3 { font-size: var(--font_size_h3); }
 h4, h5, h6 { color: crimson; } /* dot not use h4-h6 */
+li + li { margin-top: var(--list_item_margin_top); }
 
 .reset_a a{ text-decoration: none; }
 .reset_a a:visited{ color:black; }
@@ -58,15 +60,6 @@ figcaption {
   padding-left: 5pt;
 }
 
-/* not yet working */
-/* figcaption.cap_zig { */
-/*   background: #fcdba5; */
-/* } */
-/* figcaption.cap_shell { */
-/*   background: #ccc; */
-/*   color: #000; */
-/* } */
-
 pre,
 code {
   font-size: 12pt;
@@ -94,7 +87,7 @@ code {
   border-top-right-radius: 5px;
 }
 
-/**Treesitter grammar is uncapable to disting function within call context and
+/**Treesitter grammar is uncapable to distinguish function within call context and
  * function declaration/definition. Both example and print are identified with
  * the same span class function and thus colored with --darkred:
  * fn ->example<-() void {

content/articles/ci_library.smd

@@ -2,9 +2,9 @@
 .title = "Towards an extensible continuous integration library.",
 .description = "Personal Website",
 .author = "Jan Philipp Hafer",
-.date = @date("2024-11-10T00:00:00"),
+.date = @date("2024-06-28T00:00:00"),
 .layout = "article.shtml",
-.tags = ["home", "overview", "blog posts", "articles"],
+.tags = ["article", "system", "software", "design", "continuous integration", "library"],
 .draft = false,
 ---
 

content/articles/optimal_debugging.smd

@@ -1,9 +1,9 @@
 ---
 .title = "Towards optimal an optimal debugging library framework",
 .author = "Jan Philipp Hafer",
-.date = @date("2024-04-20:00:00:00"),
+.date = @date("2024-06-28:00:00:00"),
 .layout = "optimal_debugging.shtml",
-.tags = ["article", "system", "hardware", "software", "design", "debugging"],
+.tags = ["article", "system", "hardware", "software", "design", "debugging", "library"],
 .draft = false,
 ---
 
@@ -128,16 +128,16 @@ executing the source code semantics or formal verification of the compiler
 itself, which shall not be discussed here. This leaves hardware problems,
 kernel problems, resource leaks, freezes, performance problems and logic
 problems. TODO: what they have in common + motivation TODO: Uniform execution
-representation and queries over program execution. 
+representation and queries over program execution.
 
 []($section.id("abstraction_problems"))
 ### Abstraction problems during problem isolation
 
-TODO: origin detection, isolation and abstraction 
+TODO: origin detection, isolation and abstraction
 
 []($section.id("possible_implementations"))
 ### Possible implementations
 
 TODO: (query system data vs modify the system vs other) to validate approaches;
-Program modification and validation language, query language and alternatives. 
+Program modification and validation language, query language and alternatives.
 

content/articles/process_behavior.smd

@@ -2,16 +2,16 @@
 .title = "Process semantics and abstraction problems on Linux, Windows, MacOS, Posix.",
 .description = "Personal Website",
 .author = "Jan Philipp Hafer",
-.date = @date("2024-11-10T00:00:00"),
+.date = @date("2024-06-28T00:00:00"),
 .layout = "article.shtml",
-.tags = ["article", "system", "platform", "windows", "macos", "linux", "posix", "process", "abstraction"],
+.tags = ["article", "system", "software", "design", "platform", "windows", "macos", "linux", "posix", "process", "abstraction"],
 .draft = false,
 ---
 
 This article documents process semantic differences between
 Linux, Windows, MacOS, Posix including what can be reasonably relied on and what no.
 
-TODO motivation: audience/why this is actually relevant to read, ie security. 
+TODO motivation: audience/why this is actually relevant to read, ie security.
 
     IPC.
         Signals.

content/articles/shennanigans_in_c.smd

@@ -73,14 +73,14 @@ abbreviated via macro `NULL`.
 **The Exceptions**
 - Controlling the build system and compiler invocation to opt-out of provenance based optimizations.
   1. Clang and gcc have `-fno-strict-aliasing`, msvc and tcc do disable type-based aliasing analysis based optimizations.
-  2. As of 20240603, there is no switch to disable provenance-based alias analysis in compilers (clang, gcc, msvc, tcc).
+  2. As of 2024-06-03, there is no switch to disable provenance-based alias analysis in compilers (clang, gcc, msvc, tcc).
   3. Usage of `restrict` can be en/disabled in all compilers via `#pragma optimize("", on/off)`.
   It can also be disabled in all compilers via `#define restrict`, using an according optimization level (typical `-O1`)
   or via separating header and implementation and disabling link time optimziations.
 - Posix extension and Windows in practice enable dynamic linking via casting pointers `void *` to function pointers and
   back. This also means that `sizeof (function pointer) == sizeof (void *)` must be uphold, which is not true for
   microcontrollers with separate address space for code and data or CHERI in mixed capability mode/hybrid compilation mode.
-  Address space annotations are mandatory for this to work and it is unfortunate that standards do not reflect this as of 20240428.
+  Address space annotations are mandatory for this to work and it is unfortunate that standards do not reflect this as of 2024-04-28.
 [aliasing_exceptions_uniform_address_space.c]($code.asset('./aliasing_exceptions_uniform_address_space.c').language('c'))
 
 []($section.id("pointer_construction_requirements"))
@@ -133,7 +133,7 @@ The following special cases of pointer operations can be taken into account, whe
     and upper address bound, permissions masks, flags usable for OS or application tasks, see "Capability Hardware Enhanced RISC Instructions:
     CHERI Instruction-Set Architecture (Version 9)". Since there is no formal model on how CHERI pointer semantics work, examples are not included.
     A work in progress CHERI C is given in paper "Formal Mechanised Semantics of CHERI C: Capabilities, Undefined Behaviour, and Provenance".
-    CHERI offers (scalable) compartmentalization, spatial memory safety with opt-in temporal memory safety via runtime support mandating pointer capability revocation on freeing memory with latest example being CheriBSD experimental userspace temporal memory safety (20240602).
+    CHERI offers (scalable) compartmentalization, spatial memory safety with opt-in temporal memory safety via runtime support mandating pointer capability revocation on freeing memory with latest example being CheriBSD experimental userspace temporal memory safety (2024-06-02).
 - 7.What to expect for the future.  
     LLVM support for full restrict has been merged, but
     [it has design and quality problems](https://www.reddit.com/r/rust/comments/1ft619r/llvm_rfc_improvements_to_capture_tracking/),

content/articles/shennanigans_in_cpp.smd

@@ -1,7 +1,7 @@
 ---
 .title = "Some C++ footgun avoidance.",
 .author = "Jan Philipp Hafer",
-.date = @date("2024-04-20:00:00:00"),
+.date = @date("2024-04-15:00:00:00"),
 .layout = "article.shtml",
 .tags = ["article", "c++", "software", "design"],
 .draft = false,
@@ -19,8 +19,8 @@ consider taking a look at the
 and [preprocessor iceberg](https://github.com/JadLevesque/PPMP-Iceberg).
 
 []($section.id("cpp_review"))
-Update 20241217:
-Since the writing of this article (20240618), I did significantly
+Update 2024-12-17:
+Since the writing of this article (2024-04-15), I did significantly
 extend my CI-tested sample code on C++14, C++17, C++20 and
 C++23 and do not plan to continue to list footguns.
 My main complains about C++ are

content/articles/shennanigans_in_python.smd

@@ -29,7 +29,7 @@ to collect context (information along multiple functions, for example from
 different combination of traversal) becomes unreasonably verbose and error
 prone. The alternative is to use C-like error handling, which requires to figure out
 all possible exceptions of Python libstd methods, which language servers
-do not support (as of 20240404).
+do not support (as of 2024-04-04).
 
 []($section.id("list_of_shennanigans"))
 Aside of these more fundamental limitations, here the [list of shennanigans](#list_of_shennanigans) I have run into:

content/articles/shennanigans_in_zig.smd

@@ -8,7 +8,7 @@
 ---
 
 []($section.id("intro"))
-As of ~~20240404 (zig version 0.12.0-dev.3562+96bc8f17c)~~ 20240701 (zig version 0.14.0-dev.4234+1e3fb4825),
+As of ~~2024-04-04 (zig version 0.12.0-dev.3562+96bc8f17c)~~ 2024-07-01 (zig version 0.14.0-dev.4234+1e3fb4825),
 * Zig provides
   one of the best possible semantics to optimize memory details, while
   offering widely portable source code with reasonable safety in a
@@ -22,29 +22,29 @@ very flexible and cryptic syntax of C (see [preprocessor iceberg](https://github
 - Bottlenecks of array assignments not obvious via <code>@memcpy</code>:
 [perf_array_assignment.zig]($code.asset('./perf_array_assignment.zig').language('zig'))
 - Signaling: Test runner allows no signaling to <code>qemu -g
-  4242</code> (debugger mode). Qemu uses gdb server signaling, 
+  4242</code> (debugger mode). Qemu uses gdb server signaling,
   which means sending SIGKILL is necessary to kill
   the debugging server process.
-- Memory, aliasing and pointer semantics: Zig inherits from LLVM potential 
-  miscompilations due to longstanding provenance and aliasing bugs. (Updated 20240701)
+- Memory, aliasing and pointer semantics: Zig inherits from LLVM potential
+  miscompilations due to longstanding provenance and aliasing bugs. (Updated 2024-07-01)
   * [Zig upstream issue](https://github.com/ziglang/zig/issues/20198)
   * [LLVM upstream issue](https://github.com/llvm/llvm-project/issues/33896)
   * [Related Rust RFC](https://rust-lang.github.io/rfcs/3559-rust-has-provenance.html)
   * [Related gcc issue](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105294#c2)
-- Weak memory semantics: Zig inherits from LLVM the same class of problems 
-  from the C11 memory model. As of 20240701, and take below statements with a 
-  big grain of salt, since I did not check thoroughly common vendors and I do 
-  mostly rely on talks from ACM SIGPLAN FOWM'24 and "Multicore Semantics: 
-  Making Sense of Relaxed Memory". (Updated 20240701)
-  * There is nothing conclusive on how the "out of thin air problem" should be 
+- Weak memory semantics: Zig inherits from LLVM the same class of problems
+  from the C11 memory model. As of 2024-07-01, and take below statements with a
+  big grain of salt, since I did not check thoroughly common vendors and I do
+  mostly rely on talks from ACM SIGPLAN FOWM'24 and "Multicore Semantics:
+  Making Sense of Relaxed Memory". (Updated 2024-07-01)
+  * There is nothing conclusive on how the "out of thin air problem" should be
   fixed, which is problematic for reasoning with weak memory.
-  * Many hardware architectures have no sufficiently ISA-complete (and formally 
+  * Many hardware architectures have no sufficiently ISA-complete (and formally
   verified) synchronization models.
-  * There is no official test corpus to stress test architectures by vendors or 
+  * There is no official test corpus to stress test architectures by vendors or
   third parties.
-  * There is no official test corpus with code and optimization models to test 
+  * There is no official test corpus with code and optimization models to test
   formal model influence of example code.
-  * There is no debugging tooling to identify and trace or track down 
-  synchronization bugs from weak memory (in production) or vendor recommended 
-  strategies to stress test on their platforms (derived from the formal models 
+  * There is no debugging tooling to identify and trace or track down
+  synchronization bugs from weak memory (in production) or vendor recommended
+  strategies to stress test on their platforms (derived from the formal models
   of the architecture).

content/articles/using_zine.smd

@@ -7,7 +7,7 @@
 .draft = false,
 ---
 
-This is a brief experience report on usage of zine as static website generator from 20241220.
+This is a brief experience report on usage of zine as static website generator from 2024-12-20.
 
 My main use cases are
 

content/index.smd

@@ -9,16 +9,16 @@
 ---
 
 ### [Articles]($section.id('home_left'))
-* 20240420 - [Python shennanigans.](./articles/shennanigans_in_python)
-* 20240420 - [Zig shennanigans.](./articles/shennanigans_in_zig)
-* 20240415 - [Some C++ footgun avoidance.](./articles/shennanigans_in_cpp)
-* 20240428 - [C shennanigans: Pointers, sequence points and bit fields.](./articles/shennanigans_in_c)
-* 20240628 - [Towards an optimal debugging framework library.](./articles/optimal_debugging)
+* 2024-04-20 - [Python shennanigans.](./articles/shennanigans_in_python)
+* 2024-04-20 - [Zig shennanigans.](./articles/shennanigans_in_zig)
+* 2024-04-15 - [Some C++ footgun avoidance.](./articles/shennanigans_in_cpp)
+* 2024-04-28 - [C shennanigans: Pointers, sequence points and bit fields.](./articles/shennanigans_in_c)
+* 2024-06-28 - [Towards an optimal debugging framework library.](./articles/optimal_debugging)
   - wip practice, uniform execution representations, abstraction problems, implementation options
-* 20240628 - [Process semantics and abstraction problems on Linux, Windows, MacOS, Posix.](./articles/process_behavior)
+* 2024-06-28 - [Process semantics and abstraction problems on Linux, Windows, MacOS, Posix.](./articles/process_behavior)
   - wip IPC, security, process groups, abstraction problems
-* 20240628 - [Towards an extensible continuous integration library.](./articles/ci_library)
+* 2024-06-28 - [Towards an extensible continuous integration library.](./articles/ci_library)
   - wip motivation, maintenance, security, remote debugging, untrusted OSes
 
 ### [Posts]($section.id('home_right'))
-* 20241219 - [Using zine.](./articles/using_zine)
+* 2024-12-19 - [Using zine.](./articles/using_zine)