Re: RISC-V animals sporadically produce weird memory-related failures

2024-12-02 Thread Alexander Lakhin
02.12.2024 18:25, Tom Turelinckx wrote: These crashes are hardly related to code changes, so maybe there are platform-specific issues still... I naively assumed that because llvm and clang are available in Trixie on riscv64 that I could simply install them and enable --with-llvm on copperhead,

Re: RISC-V animals sporadically produce weird memory-related failures

2024-12-02 Thread Tom Turelinckx
Hi Alexander, On Mon, Dec 2, 2024, at 2:00 PM, Alexander Lakhin wrote: > These crashes are hardly related to code changes, so maybe there are > platform-specific issues still... I naively assumed that because llvm and clang are available in Trixie on riscv64 that I could simply install them and

Re: RISC-V animals sporadically produce weird memory-related failures

2024-12-02 Thread Thomas Munro
On Tue, Dec 3, 2024 at 7:00 AM Alexander Lakhin wrote: > A build made with clang-19 without llvm passed `make check` successfully. We heard in another thread[1] that we'd need to use the JITLink API for RISCV, instead of the RuntimeDyld API we're using. I have a newer patch to use JITLink on all

Re: RISC-V animals sporadically produce weird memory-related failures

2024-12-02 Thread Alexander Lakhin
Hello Tom, 17.11.2024 20:28, Tom Turelinckx wrote: I have now done just that, but on a new HiFive Premier P550 board [2]. It is running Ubuntu 24.04 LTS with a board-specific kernel, currently 6.6.21-9-premier (2024-11-09). The buildfarm client is executing within a Debian Trixie container cr

Re: RISC-V animals sporadically produce weird memory-related failures

2024-11-17 Thread Tom Turelinckx
Hello Alexander, On Thu, Aug 22, 2024, at 11:00 AM, Alexander Lakhin wrote: > Dear copperhead, boomslang owner, could you consider upgrading OS on > these animals to rule out effects of OS anomalies that might be fixed > already? If it's not an option, couldn't you perform stress testing of > thes