!xmLtiCaAJxfhURjrXl:matrix.org

NixOS RISC-V

227 Members
NixOS on RISC-V https://wiki.nixos.org/wiki/RISC-V https://pad.lassul.us/NixOS-riscv64-linux https://github.com/orgs/NixOS/teams/risc-v66 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
4 Apr 2024
@hive:the-apothecary.clubπŸ‘‰@crystallinefire:chat.solarpunk.moethis is going to make things difficult,,,18:07:19
@hive:the-apothecary.clubπŸ‘‰@crystallinefire:chat.solarpunk.moecatch2-3.5.2-riscv64-linux18:07:20
@sorear:matrix.orgsorear

the C910 has two classes of issues:

  1. non-standard features for things that eventually became standard, i.e. RVV 0.7.1, MAEE instead of Svpbmt (needed for PCIe because Intel didn't distinguish BARs by memory type, irrelevant otherwise), T-Head performance counters, etc. None of this affects software that doesn't opt in to using the pre-standard feature, and none of it is morally different from any other non-standard extension, which are likely to be ubiquitous
  2. ordinary bugs - unreasonably slow contended memory access without fences, wrong decoding of noncanonical fences, wrong FP underflow flag - there is no reason to believe that future, more complicated cores will have fewer total bugs, even if they fix the current bugs, and also no evidence that the C910's crop of bugs can cause successful builds with miscompilations
18:24:49
@sorear:matrix.orgsorearI can't imagine a consistent standard which would (a) rule out the use of the C910 for non-test builds (b) not rule out every other piece of hardware which exists in the past and future for the same reason18:25:50
@thefossguy:matrix.orgPratham PatelThe SiFive J74 cores in the Unmatched and the VF2 are pretty spec compliant AFAIK18:30:07
@sorear:matrix.orgsorearare those the ones that can't correctly handle a sfence instruction with a nonzero virtual address and get the trap PC wrong when you jump to a negative noncanonical VA?18:32:03
@sorear:matrix.orgsorearsifive is better at communicating errata in english, I'll give them that much18:32:36
@sorear:matrix.orgsorearI specifically want to avoid a policy which requires no public errata, because that will just push us towards vendors that treat all errata as trade secrets18:33:04
@thefossguy:matrix.orgPratham Patel me not know that, I’ll look into that tomorrowΒ  18:34:07
@alex:tunstall.xyzAlex
In reply to @hive:the-apothecary.club
catch2-3.5.2-riscv64-linux
I've already encountered this build failure. Here's a fix (probably suboptimal, but it works).
19:18:21
@hive:the-apothecary.clubπŸ‘‰@crystallinefire:chat.solarpunk.moethanks :fold19:19:44
@hive:the-apothecary.clubπŸ‘‰@crystallinefire:chat.solarpunk.moe* thanks πŸ™19:19:49
@alex:tunstall.xyzAlex(The fix is based on skeuchel's PR. You could probably use that PR directly if you use a custom Nixpkgs repository; I don't.)19:20:37
@hive:the-apothecary.clubπŸ‘‰@crystallinefire:chat.solarpunk.moei don't either19:20:50
@darinmorrison:matrix.orgsilvanshade joined the room.19:42:09
5 Apr 2024
@liberodark:matrix.orgliberodark joined the room.07:46:35
@liberodark:matrix.orgliberodarkHi11:27:42

Show newer messages


Back to Room ListRoom Version: 10