public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98895] C++ module generates too many dead code Date: Fri, 29 Jan 2021 21:49:47 +0000 [thread overview] Message-ID: <bug-98895-4-7VzLbrU1Q2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98895-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98895 cqwrteur <unlvsur at live dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |All Host| |All --- Comment #1 from cqwrteur <unlvsur at live dot com> --- #include<stdio.h> inline void test(char const* str) noexcept { puts(str); } int main() { test("Hello\n"); } hello.cc module; #include<stdio.h> export module hello; export inline void test(char const* str) noexcept { puts(str); } main.cc import hello; int main() { test("Hello\n"); } The 2nd generates a larger binary because it emits dead module entry. Please remove all dead code thank you.
next prev parent reply other threads:[~2021-01-29 21:49 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-29 21:46 [Bug c++/98895] New: " unlvsur at live dot com 2021-01-29 21:49 ` unlvsur at live dot com [this message] 2021-01-30 9:38 ` [Bug c++/98895] " pilarlatiesa at gmail dot com 2022-11-03 13:12 ` ppalka 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-98895-4-7VzLbrU1Q2@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: linkBe 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).