public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59394] Unused code generated
Date: Sun, 22 Dec 2013 16:43:00 -0000	[thread overview]
Message-ID: <bug-59394-4-D9ZkGyfWTG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59394-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59394

--- Comment #3 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
Some more notes:

If you don't want that small functions are being inlined, consider
-fno-inline-small-functions.

If a function is being inlined then it's body is still implemented except in
the case where GCC can prove the body is never needed, for example if the
function is static.

If you implement two functions that result in the same code, GCC won't reuse
the code for you.  If you have redundant code, it is up to you to reuse it.


  parent reply	other threads:[~2013-12-22 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 11:06 [Bug c++/59394] New: " smal.root at gmail dot com
2013-12-05 11:07 ` [Bug c++/59394] " smal.root at gmail dot com
2013-12-22 15:11 ` gjl at gcc dot gnu.org
2013-12-22 15:12 ` gjl at gcc dot gnu.org
2013-12-22 16:43 ` gjl at gcc dot gnu.org [this message]
2021-12-23  7:00 ` [Bug middle-end/59394] " pinskia at gcc dot gnu.org
2021-12-23  8:02 ` smal.root at gmail dot com
2021-12-23  8:04 ` smal.root at gmail dot com

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-59394-4-D9ZkGyfWTG@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).