From 8ea01a571be073be00f8a77150f3d62ef5600b52 Mon Sep 17 00:00:00 2001 From: Nicolas James Date: Thu, 12 Mar 2026 20:42:37 +1100 Subject: Fix potential clock domain mismatch when using chrono::now() --- src/queue_context.hh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/queue_context.hh') diff --git a/src/queue_context.hh b/src/queue_context.hh index fbb04e8..0e6441e 100644 --- a/src/queue_context.hh +++ b/src/queue_context.hh @@ -20,7 +20,7 @@ class QueueContext final : public Context { // The amount of finished frame timing data we keep before eviction. // For now, this value is also the number of data points used in the // calculation of gpu timing information. - static constexpr auto MAX_TRACKED_TIMINGS = 50; + static constexpr auto MAX_TRACKED_TIMINGS = 50u; // The amount of queue submissions we allow tracked per queue before // we give up tracking them. For a queue that is presented to, // these submissions will be constantly moved to Frame structs so @@ -29,7 +29,7 @@ class QueueContext final : public Context { // amount of vkQueueSubmit's per frame. For queues which don't // present, this limit stops them from growing limitlessly in memory // as we may not necessarily manually evict them yet. - static constexpr auto MAX_TRACKED_SUBMISSIONS = 50; + static constexpr auto MAX_TRACKED_SUBMISSIONS = 50u; public: DeviceContext& device_context; -- cgit v1.2.3