More support for finding original source code from transformed code
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No specific file, test, or entry point is identified. Start by tracing how transformed source is generated, then investigate how original Fortran line information could be retained through transformations toward SIR or CUDA and exposed for a C stack trace. Done would mean defining and implementing a reliable way to find the original source location from transformed-code line information.
Written by the indexing model from the issue text.
Description
During my presentation the issue was raised by a user that it might be difficult to understand a crash: it will provide a line number that is potentially completely useless in the original source code.
It could be useful if we could 'annotate' our transformed source code with the original line numbers. So if the binary crashes, we look at the line number in the transformed code, to easily find the original code.
This is probably not an issue for a CS debugging transforms or so, but could be useful for natural scientists to find science problems (NANs, unstable solutions or so)?
ATM most transforms leave the code similar enough to identify the original code. But if we think of going via SIR to cuda ... then having a potential way of finding from a C stack trace the original Fortran lines could be quite useful.
- Dominant language
- Python
- Stars
- 137
- Forks
- 36
- Avg merge
- 6d 16h
- Merged PRs (30d)
- 18
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stfc/PSyclone
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
frontend: add support for ALOG, ALOG10 and IDInt intrinsics. Specify FLOAT as available on GPU. Openenhancement PSyIR
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
NEMO
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100