Description

We tried to create a CI for Windows. It was a simple build CI. It would build JuleC from the IR code and rebuild and compile the latest JuleC from source. But we had some problems.

This CI gets the latest windows-amd64 with CURL from Julec-IR repository and compiles via GCC with O3, -w, -Wa,-mbig-obj and C++17. After compiling the IR code obtained with CURL, a simple command is executed for testing. A simple julec version command is then executed. However, the execution of the program results in failure.

We left only the header files and an empty entry point, as we thought this could be caused by some algorithms in the IR code. Then we removed all header files. It was the inclusion of the API that was causing the problem. However, we had a program that did nothing. There was an empty entry point. From what we analyzed, the API did not have code that would lead to the execution of an algorithm that could cause problems when just included. So the program wasn't really doing anything as far as we know.

This issue could be a minor overlooked bug, a simple programming error in the API, or something that has nothing to do with us directly, such as a GCC compilation issue. We tried to do various things to understand this problem, but we couldn't find a rational point to start fixing it. Needs more research.

Expected behavior

Program should execute as expected.

Current behavior

Each execution's result is Process completed with exit code -1073741511 or something like that.

Additional information

The current situation when we do this:

• Commit of Jule repository: 79c36b2e9e
• Commit of Julec-IR repository: 9ab7a750fc