public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "euloanty at live dot com" <gcc-bugzilla@gcc.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 18:57:48 +0000	[thread overview]
Message-ID: <bug-95917-4-OlYUvj7JoP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95917-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95917

--- Comment #3 from fdlbxtqi <euloanty at live dot com> ---
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?

https://github.com/isocpp/CppCoreGuidelines/issues/1630

YES! INLINE ALL YOUR FUNCTIONS. AVOID function pointers and virtual functions
as plagues.

  parent reply	other threads:[~2020-06-26 18:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 18:44 [Bug c++/95917] New: " euloanty at live dot com
2020-06-26 18:51 ` [Bug c++/95917] " euloanty at live dot com
2020-06-26 18:54 ` euloanty at live dot com
2020-06-26 18:57 ` euloanty at live dot com [this message]
2020-06-26 19:01 ` iains at gcc dot gnu.org
2020-06-26 19:03 ` euloanty at live dot com
2020-06-26 19:12 ` euloanty at live dot com
2020-06-27  7:31 ` redi at gcc dot gnu.org
2020-10-20 10:13 ` [Bug libstdc++/95917] " redi at gcc dot gnu.org
2020-10-20 10:38 ` cvs-commit at gcc dot gnu.org
2020-10-20 10:40 ` redi at gcc dot gnu.org

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=bug-95917-4-OlYUvj7JoP@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).