Skip to content

[mono] [RISC-V] re-implement floating point arithmetic without r4fp - #84470

Merged
vargaz merged 3 commits into
dotnet:mainfrom
Xinlong-Wu:fix-no-r4fp
Apr 8, 2023
Merged

[mono] [RISC-V] re-implement floating point arithmetic without r4fp#84470
vargaz merged 3 commits into
dotnet:mainfrom
Xinlong-Wu:fix-no-r4fp

Conversation

@Xinlong-Wu

Copy link
Copy Markdown
Contributor

This patch re-implement floating point arithmetic for RISC-V as #84418 mentioned

@ghostghost added area-VM-meta-mono community-contribution Indicates that the PR has been added by a community member labels Apr 7, 2023
@vargaz

Copy link
Copy Markdown
Contributor

mini-riscv.h needs to define
#define MONO_ARCH_FLOAT32_SUPPORTED 1

@am11am11 added the arch-riscv Related to the RISC-V architecture label Apr 7, 2023
@vargaz
vargaz merged commit 568292a into dotnet:mainApr 8, 2023
@Xinlong-Wu
Xinlong-Wu deleted the fix-no-r4fp branch April 8, 2023 05:24

case OP_IMUL:
case OP_LMUL:
case OP_RMUL:

@am11am11Apr 25, 2023

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Xinlong-Wu, can we also handle long_mul_ovf_un here? In qemu, I'm getting:

# built with runtimeFlavor: mono
$ /runtime/artifacts/bin/testhost/net8.0-linux-Debug-riscv64/dotnet \
bin/Release/net8.0/helloworld.dll
Can't decompose the OP long_mul_ovf_un* Assertion: should not be reached at /runtime/src/mono/mono/mini/mini-riscv.c:1731=================================================================	Native Crash Reporting=================================================================Got a SIGABRT while executing native code. This usually indicates...

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure,I will submit a pr of the progress so far.
I think it may fix this problem.
And I plan to use monthly and half monthly pr to synchronize changes in the future

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

have submit a pr #85445
Now we are searching for when to push/pop lmf so that tey-catch can be executed correctly and mono can print the call stack correctly.

@ghostghost locked as resolved and limited conversation to collaborators May 27, 2023
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

arch-riscvRelated to the RISC-V architecturearea-VM-meta-monocommunity-contributionIndicates that the PR has been added by a community member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@Xinlong-Wu@vargaz@am11