synchronized is a Java keyword, enforcing mutual exclusion for a critical section via some object's intrinsic lock.
Note 1: ETH::2. Semester::PProg
Deck: ETH::2. Semester::PProg
Note Type: Horvath Cloze
GUID:
modified
Note Type: Horvath Cloze
GUID:
d?(F&:%xxs
Before
Front
Back
synchronized is a Java keyword, enforcing mutual exclusion for a critical section via some object's intrinsic lock.
After
Front
synchronized is a Java keyword, enforcing mutual exclusion for a critical section via some object's intrinsic lock.
Back
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 |
{{c1::synchronized}} is a Java keyword, enforcing {{c2::mutual exclusion for a critical section via some object's intrinsic lock}}. |
Note 2: ETH::2. Semester::PProg
Deck: ETH::2. Semester::PProg
Note Type: Horvath Cloze
GUID:
modified
Note Type: Horvath Cloze
GUID:
fcsPFI,=e0
Before
Front
Locality has several meanings in parallel programming:
- Locally reason about one thread at a time (thread modularity) - simplifies correctness arguments.
- Data locality: related memory locations are accessed shortly after each other - improves cache usage
- Code locality: straight-line code increases opportunities for instruction level parallelism.
Back
Locality has several meanings in parallel programming:
- Locally reason about one thread at a time (thread modularity) - simplifies correctness arguments.
- Data locality: related memory locations are accessed shortly after each other - improves cache usage
- Code locality: straight-line code increases opportunities for instruction level parallelism.
After
Front
Locality has several meanings in parallel programming:
- Locally reason about one thread at a time (thread modularity) - simplifies correctness arguments.
- Data locality: related memory locations are accessed shortly after each other - improves cache usage
- Code locality: straight-line code increases opportunities for instruction level parallelism.
Back
Locality has several meanings in parallel programming:
- Locally reason about one thread at a time (thread modularity) - simplifies correctness arguments.
- Data locality: related memory locations are accessed shortly after each other - improves cache usage
- Code locality: straight-line code increases opportunities for instruction level parallelism.
Field-by-field Comparison
| Field | Before | After |
|---|---|---|
| Text | 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> |
Note 3: ETH::2. Semester::PProg
Deck: ETH::2. Semester::PProg
Note Type: Horvath Cloze
GUID:
modified
Note Type: Horvath Cloze
GUID:
kaCb;PSfJ_
Before
Front
A safety property is a property of a system: nothing bad ever happens".
Back
A safety property is a property of a system: nothing bad ever happens".
Can be violated in finite time.
After
Front
A safety property is a property of a system: "nothing bad ever happens".
Back
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"}}. | A {{c1::safety property}} is {{c2::a property of a system: "nothing bad ever happens"}}. |