From: Wilhelm Meier <wilhelm.meier@hs-kl.de>
To: <gcc-help@gcc.gnu.org>
Subject: Re: Use coroutines for avr-gcc
Date: Thu, 22 Sep 2022 14:28:57 +0200 [thread overview]
Message-ID: <d9929416-714b-b24b-aef0-b2350453b053@hs-kl.de> (raw)
In-Reply-To: <b406c246-adba-251f-0763-c32b93620e92@hs-kl.de>
According to the standard, an implementation can avoid the
heap-allocation, if
- the lifetime of the coroutine is strictly within the lifetime of the
caller
- the size of coroutine state can be determined at compile time
Looks like this optimization is not yet available because new/delete-ops
are required.
Is there any work on this topic?
Thanks!
Wilhelm
On 21.09.22 15:38, Wilhelm Meier wrote:
> I tried to use coroutines with avr-gcc (13.0.0) for the AVR target. I
> managed to include the coroutine-header and to write a very simple
> generator using the example from cppreference.
>
> It compiles well, but then I get undefined symbols:
>
> 1) new and delete operator-functions
> 2) f(f()::f().Frame*)
>
> Therefore two question arise here:
>
> a) is it possible to use coroutines without head-allocation? E.g. define
> some global storage for the state of the coroutine?
> b) if a) can be fullfilled, what is 2) supposed to do?
>
> Thanks for any hints,
> Wilhelm
next prev parent reply other threads:[~2022-09-22 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 13:38 Wilhelm Meier
2022-09-22 12:28 ` Wilhelm Meier [this message]
2022-09-22 12:34 ` Jonathan Wakely
2022-09-22 19:58 ` Iain Sandoe
2022-09-23 7:58 ` Wilhelm Meier
2022-09-23 8:16 ` Iain Sandoe
2022-09-23 8:42 ` Wilhelm Meier
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=d9929416-714b-b24b-aef0-b2350453b053@hs-kl.de \
--to=wilhelm.meier@hs-kl.de \
--cc=gcc-help@gcc.gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).