[opencl] account for variable precision in backend

Open
#592 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

No file, test, or entry point is named. Start by tracing the OpenCL backend's use of symbol-table precision and determine how PSyclone configuration should define mappings such as r_def to OpenCL types; done means variable precision is respected rather than assuming all reals are 64-bit.

Written by the indexing model from the issue text.

Description

Currently the OpenCL backend simply ignores any precision information in the symbol table and assumes that all reals are 64-bit. What we really should do is examine the precision information and robustly map from that to the appropriate OpenCL types. This will probably require configuration information to be provided to PSyclone (e.g. that a precision of r_def == 64-bit real).

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.