rust-lang / rust-lang/rustc_apfloat
Consider fuzzing `ppc::DoubleDouble` as well, not just `ieee` formats.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 23
- Forks
- 16
- Avg merge
- 6h 52m
- Merged PRs (30d)
- 1
Description
The obvious benefit of testing/fuzzing is almost entirely limited to IEEE and IEEE-style formats (even odd ones can still exercise code paths common to all IEEE floats - that's how https://github.com/llvm/llvm-project/issues/63895 was found).
But because we're not fuzzing PPC's weird "double double" (i.e. (f64, f64)) format, and the upstream tests are pretty lacking, we're still liable to have random bugs laying around, e.g. https://github.com/rust-lang/rust/pull/83725.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or test entry points; start by locating the existing fuzzing setup for IEEE and IEEE-style formats and reviewing the upstream APFloat tests. Done means PPC's (f64, f64) DoubleDouble format is covered by fuzzing and previously missed random bugs can be exercised by the new coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100