Message412679
We have an autoconf check for stdatomic.h. The test even verifies that a program with atomic_load_explicit() compiles and links.
How do we want to use mimalloc in the future? Is it going to stay optional in 3.12? Then the default setting for --with-mimalloc should depend on presence of stdatomic.h. Do we want to make it mandatory for GC heap walking and nogil? Then --with-mimalloc should default to "yes" and configure should abort when stdatomic.h is missing.
I'm leaning towards --with-mimalloc=yes. It will make users aware that they need a compiler with atomics:
configure: error: --with-mimalloc requires stdatomic.h. Update your compiler or rebuild with --without-mimalloc. Python 3.12 will require stdatomic. |
|
Date |
User |
Action |
Args |
2022-02-06 23:08:03 | christian.heimes | set | recipients:
+ christian.heimes, nascheme, corona10 |
2022-02-06 23:08:03 | christian.heimes | set | messageid: <1644188883.76.0.744306065018.issue46657@roundup.psfhosted.org> |
2022-02-06 23:08:03 | christian.heimes | link | issue46657 messages |
2022-02-06 23:08:03 | christian.heimes | create | |
|