ucb-bar / ucb-bar/berkeley-hardfloat
Discrepancy/Bug in the comparison operation
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 393
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
We suspect a possible bug in the reconversion module for double-precision inputs. The bug appears to be in the fNTorecFN module. The two inputs an and b that are being compared in the attached JasperGold snapshot are not equal, and our testbench also computes that they are not equal. However, the reconversion (recoded) module appears to make them identical after the recoding. We were expecting to see a.out and b.out to mirror a and b in terms of staying unequal.
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
Start with the fNTorecFN module and the JasperGold snapshot described in the issue, then compare a.out and b.out with the testbench's a and b values. Done means determining why unequal double-precision inputs become identical after recoding and preserving the expected inequality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100