Kevin Boos
Kevin Boos
ACPI-related crates have been reorganized. Other subsystems to follow.
HI @kavanmevada, can you kindly explain what this PR contains? It appears to consist of thousands of lines of code copied from another project (which we cannot accept due to...
So, to summarize the key points of our discussion: * Document why we have a single CSPRNG, and why we're using a CS one instead of non-CS * Describe how...
> That's because `tsc` is incorrectly infallible; it doesn't check whether the counter exists. But that's a separate issue. Hmm, i see. While that technically might be a concern for...
is the whole `hpet` usage necessary? Or can we just replicate it with a constant `u64` value?
Great, can you update the minimal example to reflect that?
The root problem as identified above is that the functions as generated within the compiler_builtins crate for `__floatdisf` (u64 -> f32) and `__floatdidf` (u64 -> f64) are _supposed_ to be...
Minimal example here: ```rust #![no_std] extern crate alloc; #[macro_use] extern crate terminal_print; use alloc::{vec::Vec, string::String}; pub fn main(_: Vec) -> isize { let u64_value: u64 = 9000000000000; println!("trying to convert...
I don't think there's much we can do for this besides wait for rustc to fix it, or submit such a fix ourselves to the compiler_builtins repo.
This has been solved in more recent compiler versions and no longer occurs.