viperproject / viperproject/silver
Macro containing calls to other macros might cause location issues
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 100
- Forks
- 53
- Avg merge
- 8h 10m
- Merged PRs (30d)
- 2
Description
The following code is causing issues in the correct line:
define A()
false
define B()
A()
method test()
{
assert B() // Issue in this line, not in the body of A or B
}
However, the file all/issues/silicon/0493c.vpr is producing some wrong locations within the error messages. This seems to be related with macros being called within macros. Although the code above works correctly with this situation, some particularity in file 0493c.vpr is causing location issues and must be investigated.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the location errors from all/issues/silicon/0493c.vpr and compare them with the provided nested-macro example. Trace how macro calls are expanded and how source locations are propagated, then verify that diagnostics for the affected cases point to the correct source lines rather than macro bodies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100