From: Stefan Hajnoczi <stefanha@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
Serge Guelton <sguelton@redhat.com>
Subject: Re: Portable inline asm to get address of TLS variable
Date: Tue, 1 Mar 2022 13:39:41 +0000 [thread overview]
Message-ID: <Yh4iHeb6FsnxLUNn@stefanha-x1.localdomain> (raw)
In-Reply-To: <8735k1q452.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
On Tue, Mar 01, 2022 at 12:54:49PM +0100, Florian Weimer wrote:
> > I took a quick look at C++20 coroutines since they are available in
> > compilers but the primitives look hard to use even from C++, let alone
> > from C.
>
> Could you go into details what makes them hard to use? Is it because
> coroutines are infectious across the call stack?
Here is the simplest tutorial on C++20 coroutines I found:
https://itnext.io/c-20-coroutines-complete-guide-7c3fc08db89d
The amount of boilerplate for trivial coroutine functions is ridiculous.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-03-01 13:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 17:46 Portable inline asm to get address of TLS variable Stefan Hajnoczi
2022-02-16 18:13 ` Florian Weimer
2022-02-16 20:28 ` Stefan Hajnoczi
2022-02-16 20:33 ` Stefan Hajnoczi
2022-02-16 20:46 ` Florian Weimer
2022-02-17 9:30 ` Stefan Hajnoczi
2022-02-16 20:40 ` Florian Weimer
2022-02-17 9:28 ` Stefan Hajnoczi
2022-02-17 11:40 ` Paolo Bonzini
2022-02-17 15:02 ` Serge Guelton
2022-02-17 15:11 ` Stefan Hajnoczi
2022-02-17 15:51 ` Paolo Bonzini
2022-02-17 14:59 ` Serge Guelton
2022-03-01 11:54 ` Florian Weimer
2022-03-01 13:39 ` Stefan Hajnoczi [this message]
2022-04-19 11:32 ` Florian Weimer
2022-04-19 18:38 ` Thomas Rodgers
2022-04-20 14:12 ` Stefan Hajnoczi
2022-02-16 22:28 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yh4iHeb6FsnxLUNn@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=fweimer@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sguelton@redhat.com \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).