-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Add riscv64 managed unwinder for cDAC #117436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
@dotnet/samsung Could you please take a look? These changes may be related to riscv64. |
@dotnet/samsung, @filipnavara, FYI. I haven't tested it with dotnet/diagnostics repo (libSOS lldb plugin) yet. But it would be easier to fine tune it once the bulk of change is in. Good thing is that it's an independent component at the moment, future replacement for existing/classic DAC. |
{CONFIG}-CLR-tests FAILEDbuildinfo.json RISC-V Release-FX-QEMU: 281132 / 282209 (99.62%)
report.xml, report.md, failures.xml, testclr_details.tar.zst RISC-V Release-FX-VF2: 380606 / 381279 (99.82%)
report.xml, report.md, failures.xml, testclr_details.tar.zst Build information and commandsGIT: |
62b5ef0
to
51149e9
Compare
RISC-V Release-CLR-QEMU: 9082 / 9112 (99.67%)
report.xml, report.md, failures.xml, testclr_details.tar.zst Build information and commandsGIT: |
RISC-V Release-FX-QEMU: 283572 / 284668 (99.61%)
report.xml, report.md, failures.xml, testclr_details.tar.zst Build information and commandsGIT: |
RISC-V Release-CLR-QEMU: 9082 / 9112 (99.67%)
report.xml, report.md, failures.xml, testclr_details.tar.zst Build information and commandsGIT: |
RISC-V Release-CLR-VF2: 9083 / 9113 (99.67%)
report.xml, report.md, failures.xml, testclr_details.tar.zst RISC-V Release-FX-QEMU: 283220 / 284300 (99.62%)
report.xml, report.md, failures.xml, testclr_details.tar.zst RISC-V Release-FX-VF2: 309598 / 311346 (99.44%)
report.xml, report.md, failures.xml, testclr_details.tar.zst Build information and commandsGIT: |
2f2e220
to
d436429
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cDAC implementation looks good module comments. I don't have as much insight into the build changes.
Thanks for adding this!
...osoft.Diagnostics.DataContractReader.Contracts/Contracts/StackWalk/Context/RISCV64Context.cs
Outdated
Show resolved
Hide resolved
...osoft.Diagnostics.DataContractReader.Contracts/Contracts/StackWalk/Context/RISCV64Context.cs
Outdated
Show resolved
Hide resolved
...osoft.Diagnostics.DataContractReader.Contracts/Contracts/StackWalk/Context/RISCV64Context.cs
Outdated
Show resolved
Hide resolved
RISC-V Release-CLR-VF2: 9083 / 9113 (99.67%)
report.xml, report.md, failures.xml, testclr_details.tar.zst Build information and commandsGIT: |
This
may help? I checked Mono.Linker.csproj's |
RISC-V Release-CLR-VF2: 9083 / 9113 (99.67%)
report.xml, report.md, failures.xml, testclr_details.tar.zst RISC-V Release-CLR-QEMU: 9082 / 9112 (99.67%)
report.xml, report.md, failures.xml, testclr_details.tar.zst Build information and commandsGIT: |
@dotnet/samsung Could you please take a look? These changes may be related to riscv64. |
1 similar comment
@dotnet/samsung Could you please take a look? These changes may be related to riscv64. |
Sorry for spam, disabled for now |
@jkoritzinsky I tried a few more things (e.g., setting If you have other ideas to make |
Thanks a lot @jkoritzinsky! Six repeated builds passed (earlier three out of five builds were failing). Can we test this change in dotnet/dotnet before merging the PR? We saw two issues earlier:
|
@am11 for 1) I would expect that doing the same |
No description provided.