On Sat, Jun 20, 2020 at 12:20:14AM +0300, Ivan Maidanski wrote:
> Please disregard my previous patch, and use the following one:
> https://github.com/ivmai/libatomic_ops/commit/f067c258d5df3dc364857c11718be4516ca73ea0.patch
>
> Karsten, could you please test it?
Hello,
will do, but it will pro
Please disregard my previous patch, and use the following one:
https://github.com/ivmai/libatomic_ops/commit/f067c258d5df3dc364857c11718be4516ca73ea0.patch
Karsten, could you please test it?
Regards,
Ivan
At the same time, I checked clang for riscv (64-bit) without patch — it works,
e.g.:
unsigned /**/ short
AO_char_fetch_and_add( volatile unsigned /**/ short *addr, unsigned /**/
short incr)
{
return __atomic_fetch_add(addr, incr, __ATOMIC_RELEASE);
}
->
AO_char_fetch_and_add(unsig
Hello Karsten,
Please test the attached patch.
(I have not tested it on riscv)
Regards,
Ivan
riscv64-fix-missing-byte-short-primitives.diff
Description: Binary data
It would to solve the issue by adding -pthread because pthread-based
implementation is not lock-free.
I have created the issue in upstream (
https://github.com/ivmai/libatomic_ops/issues/46 ).
By design of libatomic_ops, if a particular operation (e.g.
__atomic_compare_exchange_1) is not supp
control: severity 962917 important
control: tags 962917 patch
On Tue, Jun 16, 2020 at 12:40:52AM +0200, Karsten Merker wrote:
> libatomic-ops FTBFS on riscv64 due to link failures in the
> testsuite. The build log is available at
>
>
> https://buildd.debian.org/status/fetch.php?pkg=libatomic-
Source: libatomic-ops
Version: 7.6.10-1
User: debian-ri...@lists.debian.org
Usertags: riscv64
Hello,
libatomic-ops FTBFS on riscv64 due to link failures in the
testsuite. The build log is available at
https://buildd.debian.org/status/fetch.php?pkg=libatomic-ops&arch=riscv64&ver=7.6.10-1&stamp
7 matches
Mail list logo
