From: Luke Kenneth Casson Leighton Date: Sat, 28 Mar 2020 14:08:36 +0000 (+0000) Subject: mention raptorcs sponsorship X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=cb67d096734baab32ac7b03decc185f804370ff7;hp=528058371db7a84a8d85c11954b5b319639bc858;p=crowdsupply.git mention raptorcs sponsorship --- diff --git a/updates/023_2020mar26_decoder_emulator_started.mdwn b/updates/023_2020mar26_decoder_emulator_started.mdwn index 4912301..19e14fb 100644 --- a/updates/023_2020mar26_decoder_emulator_started.mdwn +++ b/updates/023_2020mar26_decoder_emulator_started.mdwn @@ -260,7 +260,25 @@ we help each other. # Sponsorship by RaptorCS with a TALOS II Workstation -TODO http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-March/005291.html +With many thanks to Timothy from +[RaptorCS](https://raptorcs.com), we've a new shiny +online server that needs +[setting up](http://bugs.libre-riscv.org/show_bug.cgi?id=265). +This machine is not just a "nice-to-have", it's actually essential for +us to be able to verify against. As you can see in the bugreport, the idea +is to bootstrap our way from running IEEE754 FP on a *POWER* system +(using typically gnu libm), verifying Jacob's algorithmic FP library +particularly and specifically for its rounding modes and exception modes. + +Once that is done, then apart from having a general-purpose library that +is compliant with POWER IEEE754 which *anyone else can use*, we can use +that to run unit tests against our[ +hardware IEEE754 FP library](https://git.libre-riscv.org/?p=ieee754fpu.git;a=summary) - +again, a resource that anyone may use in any arbitrary project - verifying +that it is also correct. This stepping-stone "bootstrap" method we are +deploying all over the place, however to do so we need access to resources +that have correctly-compliant implementations in the first place. Thus, +the critical importance of access to a TALOS II POWER9 workstation. # Epic Megagrants