------- Comment From [email protected] 2024-10-07 21:30 EDT-------
(In reply to comment #8)
> ...so this is a user source error.  The fix is:
>
> --- a/src/libpmem2/ppc64/init.c
> +++ b/src/libpmem2/ppc64/init.c
> @@ -50,7 +50,7 @@ ppc_flush(const void *addr, size_t size)
>                  * According to the POWER ISA 3.1, dcbstps (aka. dcbf (L=6))
>                  * behaves as dcbf (L=0) on previous processors.
>                  */
> -               asm volatile(__DCBF(0, %0, 6) : :"r"(uptr) : "memory");
> +               asm volatile(__DCBF(0, %0, 6) : :"b"(uptr) : "memory");
>
>                 uptr += CACHELINE_SIZE;
>         }

Actually, looking closer, this isn't what valgrind is complaining about.
I'm a looking deeper.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061913

Title:
  PMDK FTBFS on ppc64el obj_basic_integration/TEST5 crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/pmdk/+bug/2061913/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to