Test compilation of generated kernel stub code?

Open
#80 0 comments 0 reactions 2 assignees View on GitHub

@arporter is already working on this.

Since Sep 28, 2017.

Assessment

This issue has not been assessed yet.

Description

question

Currently the infrastructure we use for testing whether or not generated code compiles takes a psy object as input. This means it cannot be used to test whether the code produced by the kernel-stub generator is compilable. In principle we could lift this limitation by passing in generated code as a string (as previously suggested by @rupertford).

However, the generated kernel-stub code includes the intent of all subroutine arguments and I'm fairly sure that some compilers will complain if an argument with intent(out) is not assigned to. This may mean that we can't compile the generated kernel stub code in its current form - we would need to extend the stub generator to produce dummy assignment statements.

Dominant language
Python
Stars
137
Forks
36
Avg merge
6d 16h
Merged PRs (30d)
18

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stfc/PSyclone

All issues in stfc/PSyclone

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.