Upstream tracking issues - Githubissues

npadmana / DistributedFFT

6 stars 2 forks source link

Upstream tracking issues #59

Open ronawho opened 4 years ago

ronawho commented 4 years ago

Upstream issues this work would benefit from:

Performance:

Optimize comm patterns to avoid needing usePrimitiveComm:
- [x] https://github.com/chapel-lang/chapel/issues/14478
- [ ] https://github.com/chapel-lang/chapel/issues/14479
Enable -schpl_serializeSlices by default
- [ ] https://github.com/chapel-lang/chapel/issues/14530
Avoid need for localAccess when using direct indexing:
- [x] https://github.com/chapel-lang/chapel/issues/14480
Improve performance on InfiniBand networks:
- [ ] https://github.com/chapel-lang/chapel/issues/14438

Avoid non-user facing features:

Avoid using non user-facing features for planner lock:
- [ ] https://github.com/chapel-lang/chapel/issues/9881
- [ ] https://github.com/chapel-lang/chapel/issues/12300
Avoid using default-intent-is-ref pragma:
- [ ] https://github.com/chapel-lang/chapel/issues/13319
Add official lower-level comm operations
- [ ] https://github.com/chapel-lang/chapel/issues/13052

Elegance:

Use promoted/zippered expressions when possible instead of direct indexing
- [ ] https://github.com/chapel-lang/chapel/issues/13147

Older or not as relevant:

Reduce interference between Chapel and separate OpenMP/Pthread runtimes:
- https://github.com/chapel-lang/chapel/issues/9882