446
448
pool), so there is nothing wrong about this. The
447
449
mach_read_from_4() calls here will only trigger bogus
448
450
Valgrind memcheck warnings in UNIV_DEBUG_VALGRIND builds. */
450
452
(const byte*) src + FIL_PAGE_ARCH_LOG_NO_OR_SPACE_ID);
452
454
(const byte*) src + FIL_PAGE_OFFSET);
453
455
/* Suppress Valgrind warnings about conditional jump
454
456
on uninitialized value. */