Support for Patmos platform

[EhsanKhodadad]

No description provided.

[lhstrh]

@EhsanKhodadad, I enabled CI for you, but it looks like there are still some test failures. Please address those first.

[EhsanKhodadad]

@EhsanKhodadad, I enabled CI for you, but it looks like there are still some test failures. Please address those first.

Thank you for enabling CI. The tester has not found a header file in the t-crest repository, because t-crest hasn't cloned on the tester's machine.

[lhstrh]

Got it. Can you fix it in the workflow?

[EhsanKhodadad]

Got it. Can you fix it in the workflow?

Sure

[lhstrh]

Btw, I noticed tests in your fork were failing. Here's a fix for that: #2402

[EhsanKhodadad]

I have two questions regarding this PR:

1. Since I haven't implemented multi-thread functions and variables like mutex and thread in lf-patmos-support yet, can I bypass the tests in the concurrent folder temporarily? If so how?
2. In the regular tests, all LF apps, including my HelloPatmos.lf app is tested at the beginning of the test procedure, whereas the Patmos library, including Patmos-clang, still needs to be installed. Can I postpone their execution after the Patmos installation? (Something similar to Patmos-tests, where benchmarks are run after Patmos installation.) These tests are written in .github/workflows/c-test.yml file, while the Patmos installation is invoked by c-patmos-test.yml.

[EhsanKhodadad]

I have two questions regarding this PR:

1. Since I haven't implemented multi-thread functions and variables like mutex and thread in lf-patmos-support yet, can I bypass the tests in the concurrent folder temporarily? If so how?
2. In the regular tests, all LF apps, including my HelloPatmos.lf app is tested at the beginning of the test procedure, whereas the Patmos library, including Patmos-clang, still needs to be installed. Can I postpone their execution after the Patmos installation? (Something similar to Patmos-tests, where benchmarks are run after Patmos installation.) These tests are written in .github/workflows/c-test.yml file, while the Patmos installation is invoked by c-patmos-test.yml.

@lhstrh @erlingrj @lsk567 Could you answer these questions, please? Thanks.

[erlingrj]

I have two questions regarding this PR:

1. Since I haven't implemented multi-thread functions and variables like mutex and thread in lf-patmos-support yet, can I bypass the tests in the concurrent folder temporarily? If so how?

Check out your file CPatmosTests.java, here you explicitly run these tests with buildPatmosConcurrent remove this function and then change the CI so it doesn't try to run the gradle task associated with ut.

2. In the regular tests, all LF apps, including my HelloPatmos.lf app is tested at the beginning of the test procedure, whereas the Patmos library, including Patmos-clang, still needs to be installed. Can I postpone their execution after the Patmos installation? (Something similar to Patmos-tests, where benchmarks are run after Patmos installation.) These tests are written in .github/workflows/c-test.yml file, while the Patmos installation is invoked by c-patmos-test.yml.

You should not run any Patmos-specific tests in C/regular-tests. They should be excluded from there and only be built in there special target. Do a search for ZEPYHR_UNTHREADED in the code-base to see the additions needed to disable a test category from the regular tests (and also from the CCpp tests)

[lhstrh]

This overall look good! Let me defer to @erlingrj for final approval.

[erlingrj]

Looks good, but we should not update reactor-cpp submodule in this PR

[lhstrh]

@EhsanKhodadad, please make sure reactor-cpp points to dfdac2c.

Submodule update has been undone.

[erlingrj]

Looks good, lets merge :)

[schoeberl]

Finally, very good!