From: bugzilla-daemon@libre-riscv.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 265] New: new server from raptorcs needs set up with build/test rnvironment
Date: Sun, 22 Mar 2020 23:28:02 +0000
Message-ID: <bug-265-13@http.bugs.libre-riscv.org/> (raw)
http://bugs.libre-riscv.org/show_bug.cgi?id=265
Bug ID: 265
Summary: new server from raptorcs needs set up with build/test
rnvironment
Product: Libre-RISC-V Website
Version: unspecified
Hardware: Other
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: website
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
we have been donated access to a monster Talos II workstation with 128GB RAM
and a 24 core 4x threaded processor.
i have debian 10 ppc64 installed on it, and we need to get nmigen, and a stack
of test software compiled and running.
this invludes coriolis2, nmigen, jacob's algorithmic FP library, the works.
it is a critical resource for example in being able to verify correctness of
the IEEE754 FP library, by having a compliant system against which testing can
be done particularly for rounding modes.
also it can act as another build server.
the NVMe is only 128GB so we cannot go mad with it.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next reply index
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 23:28 bugzilla-daemon [this message]
2020-03-22 23:36 ` [libre-riscv-dev] [Bug 265] " bugzilla-daemon
2020-03-23 0:07 ` [libre-riscv-dev] [Bug 265] new server from raptorcs needs set up with build/test environment bugzilla-daemon
2020-03-23 1:53 ` bugzilla-daemon
2020-03-23 8:14 ` bugzilla-daemon
2020-03-23 9:12 ` bugzilla-daemon
2020-03-23 12:31 ` bugzilla-daemon
2020-03-23 12:50 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-265-13@http.bugs.libre-riscv.org/ \
--to=bugzilla-daemon@libre-riscv.org \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git