Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consider fuzzing `ppc::DoubleDouble` as well, not just `ieee` formats.

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust

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.

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.

Dominant language
Rust
Stars
23
Forks
16
Avg merge
14h 13m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/rustc_apfloat

All issues in rust-lang/rustc_apfloat

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.