Message311322
| Author | fweimer |
|---|---|
| Recipients | fweimer, gregory.p.smith, skrah, twouters, vstinner |
| Date | 2018-01-31.10:55:10 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1517396110.43.0.467229070634.issue31912@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
max_align_t is a bit of a kitchen sink and will specify larger and larger alignment in the future, e.g. 32-byte alignment for a complex _Float128 type (a pair of two _Float128 variables). The alignment is also not generally useful for allocations whose size is smaller than the alignment. (Many mallocs do not follow the C standard and do not provide 16-byte alignment when 8 bytes are allocated, although alignof(max_align_t) is 16.) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-01-31 10:55:10 | fweimer | set | recipients: + fweimer, twouters, gregory.p.smith, vstinner, skrah |
| 2018-01-31 10:55:10 | fweimer | set | messageid: <1517396110.43.0.467229070634.issue31912@psf.upfronthosting.co.za> |
| 2018-01-31 10:55:10 | fweimer | link | issue31912 messages |
| 2018-01-31 10:55:10 | fweimer | create | |