[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH experiment 00/35] stackless coroutine backend
|
From: |
Stefan Hajnoczi |
|
Subject: |
Re: [PATCH experiment 00/35] stackless coroutine backend |
|
Date: |
Mon, 14 Mar 2022 13:43:07 +0000 |
On Sun, Mar 13, 2022 at 04:18:40PM +0100, Paolo Bonzini wrote:
> On 3/11/22 13:17, Daniel P. Berrangé wrote:
> The question is what is easier to maintain, stack switching code that is
> becoming less and less portable (status quo with SafeStack, CET and the TLS
> issues that Stefan has worked on), a mixed C/C++ codebase (C++ coroutines),
> a custom source-to-source translator (this series). The third might be more
> fun, but it would be quite a large enterprise and the C++ compiler writers
> have already done the work.
Or a C-to-C++ translator to keep the code in C but still use C++
coroutines :). (I'm joking.)
Stefan
signature.asc
Description: PGP signature
- [PATCH 32/35] qemu_co_rwlock_wrlock, (continued)
- [PATCH 32/35] qemu_co_rwlock_wrlock, Paolo Bonzini, 2022/03/10
- [PATCH 34/35] /locking/co-rwlock/upgrade, Paolo Bonzini, 2022/03/10
- [PATCH 35/35] /locking/co-rwlock/downgrade, Paolo Bonzini, 2022/03/10
- [PATCH 33/35] qemu_co_rwlock_upgrade, Paolo Bonzini, 2022/03/10
- Re: [PATCH experiment 00/35] stackless coroutine backend, Stefan Hajnoczi, 2022/03/10