Bug 104768 - [nvptx] Exploit Independent Thread Scheduling for sm_70+
Summary: [nvptx] Exploit Independent Thread Scheduling for sm_70+
Status: UNCONFIRMED
Alias: None
Product: gcc
Classification: Unclassified
Component: target (show other bugs)
Version: 12.0
: P3 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-03 10:03 UTC by Tom de Vries
Modified: 2022-03-15 13:30 UTC (History)
0 users

See Also:
Host:
Target: nvptx
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom de Vries 2022-03-03 10:03:23 UTC
Starting with sm_70, a fundamental change in the architecture occurred, called  "Independent Thread Scheduling".  It means warps threads are no longer executing in lock-step.

We could try to exploit this in the port.

F.i., is it still necessary to emit a warp sync after a diverging branch?
Comment 1 Tom de Vries 2022-03-15 13:30:29 UTC
Hmm, reading about it a bit more, it's more about enabling algorithms that were not possible before, than about performance improvements.

So, we should aim at having test-cases, both openacc and openmp that hang on previous architectures but pass with sm_70+.