From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6915B386F83E; Fri, 26 Jun 2020 19:01:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6915B386F83E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1593198108; bh=yZ2awy9uNobZrAxV6wKK/yJERT4KRT5tOzk8+BuyfMA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=oyn1yXGOo+K7GtNQVoE5Tz8RXzHDj6MHR9IMms3MBHWb8FCAxa2W7odvBqkRug85m rilP0yTNefRK8T8cv6YMJojUxzIMVyKGb5aDekvYzGT2kg1mKUt8Qdpx3gdkcVCBa6 L+Ro1ftWMA6RY12wZuK6G2MBsQ90d/YiXZ/PyS30= From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95917] coroutine functions leak under freestanding mode causing dependencies and binary bloat. Date: Fri, 26 Jun 2020 19:01:48 +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: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2020 19:01:48 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95917 --- Comment #4 from Iain Sandoe --- (In reply to fdlbxtqi from comment #3) > Jonathan. I am MAD at you. This is absolutely your fault. I told you to > always write inline and you guys do not then allow Herb Sutter to ban me. > Here is the fault in your own controlled codebase. Are you satisfied? >=20 > https://github.com/isocpp/CppCoreGuidelines/issues/1630 >=20 > YES! INLINE ALL YOUR FUNCTIONS. AVOID function pointers and virtual > functions as plagues. 1. jonathan did not write this header - I did, 2. we all make mistakes, shouting at folks isn't the optimum way to get them fixed 3. this bloat can only occur IF you include a header you are NOT using. i.e. #include in a source that has no coroutines.=