feat(gnovm): add software floating point package

[omarsy]

Closes: #312

The idea to use softfloat and work originates from this PR: #2863

Contributors' checklist...

• Added new tests, or not needed, or not feasible
• Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory
• Updated the official documentation or not needed
• No breaking changes were made, or a BREAKING CHANGE: xxx message was included in the description
• Added references to related issues and PRs
• Provided any useful hints for running manual tests

[codecov]

Codecov Report

Attention: Patch coverage is 60.57803% with 341 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
.../gnolang/internal/softfloat/runtime_softfloat64.go	71.55%	123 Missing and 5 partials ⚠️
gnovm/pkg/gnolang/values_conversions.go	25.19%	95 Missing ⚠️
gnovm/pkg/gnolang/softfloat.go	65.78%	63 Missing and 2 partials ⚠️
gnovm/pkg/gnolang/internal/softfloat/softfloat.go	18.00%	41 Missing ⚠️
gnovm/pkg/gnolang/gonative.go	50.00%	4 Missing ⚠️
gnovm/pkg/gnolang/values.go	66.66%	4 Missing ⚠️
gnovm/pkg/gnolang/op_binary.go	85.00%	1 Missing and 2 partials ⚠️
gnovm/pkg/gnolang/op_inc_dec.go	75.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• SKIP: Do not block the CI for this PR

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🟢 The pull request head branch must be up-to-date with its base (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 The pull request was created from a fork (head branch repo: omarsy/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

The pull request head branch must be up-to-date with its base (more info)

If

🟢 Condition met
└── 🟢 On every pull request

Then

🟢 Requirement satisfied
└── 🟢 Head branch (omarsy:feat/312) is up to date with base (master): behind by 0 / ahead by 12

Manual Checks

**SKIP**: Do not block the CI for this PR

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

[petar-dambovaliev]

Good job!

[thehowl]

don't create specific types with methods; just make GetFloat32 and GetFloat64 return uint32 and uint64 and make the operations, for instance the ones in op_binary.go, directly use the softfloat package.

the custom type doesn't add much aside from wrapping the calls to the internal package, while having op_binary.go use softfloat.Lte makes very explicit what's going on.

[omarsy]

Thanks for the feedback! I introduced the custom types with methods to improve readability, as I felt it made the code clearer and more explicit about the software floating-point operations. However, I understand your point about avoiding unnecessary abstraction. I will follow the Gno code standards and adjust the implementation if you guys think this approach doesn’t align with the preferred style.

[thehowl]

Can we not use something like F32toint32 here, and all other places?

This would also avoid us having to use Trunc and Mod

[omarsy]

Don't know how you will remove the float part without a trunc ? Maybe you think about a new approach ?