P1864 Defining Target Triplets #813
Description
Denver 2019-09 Tooling Minutes for P1864
D1864R0 Defining Target Tuplets
Champion: Isabella Muerte
Minute Taker: Peter Bindels
Start Overview: 14:49
Typo: "hyper".
Is this in scope for WG21? There are a lot of other stakeholders here, such as SC22 and WG14.
Start Polling: 15:24
POLL: We want to describe the target tuplet format in some ancillary document (possibly in collaboration with other standards bodies).
| Strongly For | Weakly For | Neutral | Weakly Against | Strongly Against |
|---|---|---|---|---|
| 4 | 6 | 2 | 0 | 0 |
Attendance: 14
CONSENSUS: In favor.
POLL: We want to describe a list of target tuplets in some ancillary living document (possibly in collaboration with other standards bodies).
| Strongly For | Weakly For | Neutral | Weakly Against | Strongly Against |
|---|---|---|---|---|
| 2 | 3 | 5 | 1 | 1 |
Attendance: 14
CONSENSUS: Weakly in favor.
1st entry:
- CPU architecture (status quo).
- Architecture.
CONSENSUS: Call this architecture.
2nd entry:
- vendor (status quo)
- machine (old term)
CONSENSUS: More research needed.
3rd entry:
- operating system (status quo)
CONSENSUS: Fine with status quo.
POLL: Name of the 4th entry (vote for all the ones you can tolerate, vote as many times as you want).
- ABI (status quo) 8
- runtime 0
- environment 9
- platform 1
- object format 0
CONSENSUS: Author's choice between ABI and environment.
End: 15:40
CONSENSUS: Bring a revision of P1864R0 (Defining Target Triplets), with the guidance below, to the Tooling Study Group for further review for the Modules Ecosystem Technical Report.
- Fix the "hyper" typo.
- Call the 1st entry "architecture" instead of "CPU architecture".
- Explore other options for the 2nd entry ("vendor"/"machine").
- Call the 4th entry either "ABI" (status quo) or "environment".