Compare commits

...

2 Commits

Author SHA1 Message Date
Nicolas Sarlin
47a6da60eb chore(hpu): fix Cargo.toml for release 2025-05-19 17:47:22 +02:00
Nicolas Sarlin
9128a75094 fix(doc): uniformized readme file names 2025-05-19 15:22:05 +02:00
7 changed files with 9 additions and 9 deletions

View File

@@ -8,7 +8,7 @@ homepage = "https://www.zama.ai/"
documentation = "https://docs.zama.ai/tfhe-rs"
repository = "https://github.com/zama-ai/tfhe-rs"
readme = "README.md"
keywords = ["fully", "homomorphic", "encryption", "fhe", "cryptography", "hardware", "fpga"]
keywords = ["encryption", "fhe", "cryptography", "hardware", "fpga"]
[features]
hw-xrt = []
@@ -30,7 +30,7 @@ enum_dispatch = "0.3.13"
tracing = "0.1.40"
tracing-subscriber = { version = "0.3.18", features = ["env-filter"] }
serde = { version = "1", features = ["derive"] }
toml = { version = "0.8.*", features = [] }
toml = { version = "0.8", features = [] }
paste = "1.0.15"
thiserror = "1.0.61"
bytemuck = "1.16.0"
@@ -49,16 +49,16 @@ rayon = { workspace = true }
ipc-channel = "0.18.3"
# Dependencies used for debug feature
num-traits = { version = "*", optional = true }
num-traits = { version = "0.2", optional = true }
clap = { version = "4.4.4", features = ["derive"], optional = true }
clap-num = { version = "1.1.1", optional = true }
nix = { version = "0.29.0", features = ["ioctl", "uio"] }
# Dependencies used for rtl_graph features
dot2 = { version = "*", optional = true }
dot2 = { version = "1.0", optional = true }
bitvec = { version = "*", optional = true }
serde_json = { version = "*", optional = true }
bitvec = { version = "1.0", optional = true }
serde_json = { version = "1.0", optional = true }
# Binary for manual debugging
# Enable to access Hpu register and drive some custom sequence by hand

View File

@@ -258,4 +258,4 @@ make bench_integer_hpu
You are still waiting your FPGA board and are frustrated by lead time ?
Don't worry, you have backed-up. A dedicated simulation infrastructure with accurate performance estimation is available in tfhe-rs.
You can use it on any linux/MacOs to test HPU integration within tfhe-rs and optimized your application for HPU target.
Simply through an eye to [Hpu mockup](../../mockups/tfhe-hpu-mockup/Reaadme.md), and follow the instruction.
Simply through an eye to [Hpu mockup](../../mockups/tfhe-hpu-mockup/README.md), and follow the instruction.

View File

@@ -23,7 +23,7 @@ const FILES_TO_IGNORE: [&str; 8] = [
"tfhe-ntt/README.md",
"utils/tfhe-lints/README.md",
"CONTRIBUTING.md",
"backends/tfhe-hpu-backend/Readme.md",
"backends/tfhe-hpu-backend/README.md",
];
pub fn check_tfhe_docs_are_tested() -> Result<(), Error> {

View File

@@ -52,7 +52,7 @@ fn main() {
// Instantiate HpuDevice --------------------------------------------------
// HPU configuration knobs are retrieved from a TOML configuration file. Prebuilt configurations could be find in `backends/tfhe-hpu-backend/config_store`
// For ease of use a setup_hpu.sh script is available in repository root folder and it handle the required environment variables setup and driver initialisation
// More details are available in `backends/tfhe-hpu-backend/Readme.md`
// More details are available in `backends/tfhe-hpu-backend/README.md`
let hpu_device = HpuDevice::from_config(ShellString::new("${HPU_BACKEND_DIR}/config_store/${HPU_CONFIG}/hpu_config.toml".to_string()));
// Generate keys ----------------------------------------------------------