LUMIERA.clone/tests/core/steam/engine
Ichthyostega 9a23aa773b Invocation: analyse usage of buffer metadata entries
Code clean-up: mark all buffers with a dedicated tagging type


The point in question is: if we work the LocalTag into the type-hash,
could it be possible to miss an existing entry in the metadata registry?
This could cause two entries to be locked for a single buffer address,
leading to data corruption.

As far as I can see, in the current usage this would not happen,
but unfortunately this problem can not be ruled out, since the BufferProvider
API and protocol is designed to be open for various usage patterns.

However, the same potentially disastrous pattern could also materialise
when registering two different buffer types, and then locking each
for the same buffer location.
2024-07-28 19:29:27 +02:00
..
buffer-metadata-key-test.cpp Invocation: settle upon a way to mark the output buffer 2024-07-27 17:17:02 +02:00
buffer-metadata-test.cpp Invocation: analyse usage of buffer metadata entries 2024-07-28 19:29:27 +02:00
buffer-provider-protocol-test.cpp Invocation: clarify role of Buffer-Descriptor and Dependency-Injection 2024-07-15 18:52:59 +02:00
calc-stream-test.cpp Global-Layer-Renaming: rename namespaces 2018-11-15 23:55:13 +01:00
dispatcher-interface-test.cpp Job-Planning: rework of dispatcher and pipeline builder complete (see #1301) 2023-06-22 03:55:09 +02:00
engine-interface-test.cpp Global-Layer-Renaming: adjust namespace qualification 2018-11-15 23:59:23 +01:00
feed-manifold-test.cpp Invocation: first draft of the node builder invocation 2024-07-06 21:31:03 +02:00
job-hash-test.cpp Activity-Lang: failure will certainly not be signalled to the Job 2023-08-15 17:18:30 +02:00
job-planning-pipeline-test.cpp the new design takes the old name 2023-06-22 20:23:55 +02:00
job-planning-test.cpp Invocation: Identify parts relevant for a node builder 2024-06-25 04:54:39 +02:00
mock-dispatcher.cpp Activity-Lang: failure will certainly not be signalled to the Job 2023-08-15 17:18:30 +02:00
mock-dispatcher.hpp Scheduler: devise the arrangement of basic components 2023-06-24 03:14:17 +02:00
mock-support-test.cpp Scheduler: devise the arrangement of basic components 2023-06-24 03:14:17 +02:00
node-basic-test.cpp Invocation: Identify parts relevant for a node builder 2024-06-25 04:54:39 +02:00
node-devel-test.cpp Invocation: forge a path for integration 2024-04-23 01:13:40 +02:00
node-factory-test.cpp Invocation: forge a path for integration 2024-04-23 01:13:40 +02:00
node-input-test.cpp Invocation: forge a path for integration 2024-04-23 01:13:40 +02:00
node-linkage-test.cpp Invocation: clarify further requirements for the Level-2 builder 2024-07-06 04:37:36 +02:00
node-operation-test.cpp Dispatcher-Pipeline: prepare test for the new NodeGraphAttachment 2023-06-07 04:03:00 +02:00
scheduler-interface-test.cpp Scheduler: devise the arrangement of basic components 2023-06-24 03:14:17 +02:00
test-rand-ontology.hpp Invocation: consider what is required to setup a FeedManifold 2024-06-29 04:22:23 +02:00
testframe-test.cpp Global-Layer-Renaming: rename namespaces 2018-11-15 23:55:13 +01:00
testframe.cpp Global-Layer-Renaming: rename namespaces 2018-11-15 23:55:13 +01:00
testframe.hpp Global-Layer-Renaming: rename namespaces 2018-11-15 23:55:13 +01:00
timings-test.cpp bye bye Monad (closes #1276) 2023-06-22 20:23:55 +02:00
tracking-heap-block-provider-test.cpp Invocation: clarify role of Buffer-Descriptor and Dependency-Injection 2024-07-15 18:52:59 +02:00