SoA optimization can over-promote objects used inside loops to produce slower code
Open
bug
cpp-codegen
optimization
- Dominant language
- OCaml
- Stars
- 160
- Forks
- 59
- Avg merge
- 21h 45m
- Merged PRs (30d)
- 26
Description
Current Behavior:
See this forum thread by @mike-lawrence which contains an example that is ~5x slower at --O1 compared to the default.
Expected Behavior:
SoA optimization should not promote things being assigned to inside of a tight for loop
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 with the linked forum example and inspect open pull request #3188 for the current implementation direction. Verify with that example that SoA optimization does not promote objects assigned inside tight for loops and that the reported slowdown at --O1 is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- compilers, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100