runtimeverification / runtimeverification/mir-semantics
Address platform/target-dependent aspects of MIR (Endianness, word size)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 52
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
The information about endianness and word size determines how constants are embedded into the MIR. We should
a) extract this information in stable-mir-json
b) add this information to the configuration so it can be used when decoding constants.
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 tracing the stable-mir-json handling and the configuration path used when decoding MIR constants. Identify where endianness and word size are currently available, then verify that both are extracted and passed through configuration so constant decoding uses them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100