From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A975B3858403; Thu, 22 Sep 2022 12:22:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A975B3858403 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1663849321; bh=MwKV/gv2Plyx1IkIpiYUKJm2qt8bUsROZbaUIZBzpJc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RybiFJYh2GbJ5gurZvey1HfeUzn6OYQlnO6E7UFAUAC5W+IsaUWrYif4z8sZudVg4 qn4ePFk1qY6abZ96j8xYFnIDLYXZsY08vLZpwhcLoMQZduyBzI8agg+ulh5mWmnYXs cdy6fBeBgVm69QbdYcFdMN5pP3g1LGPwj8ugdcgc= From: "klaus.doldinger64 at googlemail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106997] Use coroutines on avr-gcc Date: Thu, 22 Sep 2022 12:21:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: klaus.doldinger64 at googlemail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106997 --- Comment #2 from Wilhelm M --- I would consider this a missed optimization rather than a bug, because the standard says, that an implementation can avoid heap allocation if: - the lifetime of the coroutine is strictly within the lifetime of the call= er - the size of coroutine state can be determined at compile time The case I tested falls within the above statement.=