Anki Deck Changes

Commit: 922ce8c8 - fixes

Author: lhorva <lhorva@student.ethz.ch>

Date: 2026-03-05T10:19:54+01:00

Changes: 3 note(s) changed (0 added, 3 modified, 0 deleted)

Note 1: ETH::2. Semester::PProg

Deck: ETH::2. Semester::PProg
Note Type: Horvath Cloze
GUID: d?(F&:%xxs
modified

Before

Front

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
synchronized is a Java keyword, enforcing mutual exclusion for a critical section via some object's intrinsic lock.

Back

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
synchronized is a Java keyword, enforcing mutual exclusion for a critical section via some object's intrinsic lock.

After

Front

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
synchronized is a Java keyword, enforcing mutual exclusion for a critical section via some object's intrinsic lock.

Back

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
synchronized is a Java keyword, enforcing mutual exclusion for a critical section via some object's intrinsic lock.
Field-by-field Comparison
Field Before After
Text {{c1::synchronized}} is a Java keyword, enforcing {{c2::mutual exclusion}} for a critical section via some object's {{c3::intrinsic lock}}. {{c1::synchronized}} is a Java keyword, enforcing {{c2::mutual exclusion for a critical section via some object's intrinsic lock}}.
Tags: ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology

Note 2: ETH::2. Semester::PProg

Deck: ETH::2. Semester::PProg
Note Type: Horvath Cloze
GUID: fcsPFI,=e0
modified

Before

Front

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
Locality has several meanings in parallel programming:

  1. Locally reason about one thread at a time (thread modularity) - simplifies correctness arguments.
  2. Data locality: related memory locations are accessed shortly after each other - improves cache usage
  3. Code locality: straight-line code increases opportunities for instruction level parallelism.

Back

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
Locality has several meanings in parallel programming:

  1. Locally reason about one thread at a time (thread modularity) - simplifies correctness arguments.
  2. Data locality: related memory locations are accessed shortly after each other - improves cache usage
  3. Code locality: straight-line code increases opportunities for instruction level parallelism.

After

Front

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
Locality has several meanings in parallel programming:
  1. Locally reason about one thread at a time (thread modularity) - simplifies correctness arguments.
  2. Data locality: related memory locations are accessed shortly after each other - improves cache usage
  3. Code locality: straight-line code increases opportunities for instruction level parallelism.

Back

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
Locality has several meanings in parallel programming:
  1. Locally reason about one thread at a time (thread modularity) - simplifies correctness arguments.
  2. Data locality: related memory locations are accessed shortly after each other - improves cache usage
  3. Code locality: straight-line code increases opportunities for instruction level parallelism.

Field-by-field Comparison
Field Before After
Text {{c1::Locality}} has several meanings in parallel programming: <br><br><ol><li>{{c2::Locally reason about one thread at a time}} (thread modularity) - simplifies correctness arguments.</li><li>{{c3::Data locality}}: related memory locations are accessed shortly after each other - improves cache usage</li><li>{{c4::Code locality}}: straight-line code increases opportunities for instruction level parallelism.</li></ol><br> Locality has several meanings in parallel programming:<br><ol><li>{{c2::Locally reason about one thread at a time}} (thread modularity) - simplifies correctness arguments.</li><li>{{c3::Data locality}}: related memory locations are accessed shortly after each other - improves cache usage</li><li>{{c4::Code locality}}: straight-line code increases opportunities for instruction level parallelism.</li></ol><br>
Tags: ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology

Note 3: ETH::2. Semester::PProg

Deck: ETH::2. Semester::PProg
Note Type: Horvath Cloze
GUID: kaCb;PSfJ_
modified

Before

Front

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
A safety property is a property of a system: nothing bad ever happens"

Back

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
A safety property is a property of a system: nothing bad ever happens"

Can be violated in finite time.

After

Front

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
A safety property is a property of a system: "nothing bad ever happens"

Back

ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
A safety property is a property of a system: "nothing bad ever happens"

Can be violated in finite time.
Field-by-field Comparison
Field Before After
Text A {{c1::safety property}} is {{c2::a property of a system: nothing bad ever happens"}}.&nbsp; A {{c1::safety property}} is {{c2::a property of a system: "nothing bad ever happens"}}.&nbsp;
Tags: ETH::2._Semester::PProg::05._Java_Threads ETH::2._Semester::PProg::Terminology
↑ Top