MoFtZ

@m4rs-mt It currently looks like an issue with the kernel launcher marshaling of the Int128 parameter. When performing Int128 operations within the kernel, it appears to work as expected. However,...

@m4rs-mt OK, so I have confirmed that this is definitely to do with the kernel parameter marshaling. ILGPU is not taking into account any structure padding/alignment.

hi @LouChiSoft. Unfortunately no, I have not spent any time in trying to resolve this issue. The first topic, getting ILGPU to work with Native AOT, could actually be harder...

hi @LouChiSoft. Since our last discussions, there was an interesting new feature that might be helpful. In C# 12, there is an experimental concept called [Interceptors](https://learn.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-12#interceptors). This would potentially make...

Added minimum required Cuda architecture and ISA to pre-generated XML. This is then used in PTXBackend to report an error if LibDevice is called, and the embedded PTX is not...

Added Tools solution to CI pipeline to ensure that breaking changes are caught.

Downgraded the pre-generated PTX to use Cuda SDK v8, which is the introduction of SM_60. This will make it compatible with all SM_60 architectures, along with the oldest drivers that...

Converted to draft, so that I can refactor the code into smaller PRs that are useful to ILGPU, independent of the pre-generated PTX.

Refactoring complete.

hi @DorloBorlo. This is likely a first chance exception that is[ caught and handled](https://github.com/m4rs-mt/ILGPU/blob/c87b0370aa9d031372a2479694881047919488ad/Src/ILGPU/Frontend/DebugInformation/DebugInformationManager.cs#L359) by ILGPU. ILGPU is trying to load debug symbols, and the call to a standard .NET...