public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rohan at rohanlean dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/55546] New: Static functions that are fully inlined can end up in the object file
Date: Fri, 30 Nov 2012 13:04:00 -0000	[thread overview]
Message-ID: <bug-55546-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55546
           Summary: Static functions that are fully inlined can end up in
                    the object file
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rohan@rohanlean.de


Created attachment 28838
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28838
A rather minimal test-case for the bug.

If a static function has its address taken in the C code, but due to
optimisations the address is never used, then the function can still end up in
the object file.  I have attached a file to demonstrate the bug.  When I
compile it with -std=c11 -O3, the resulting executable will contain code for f,
even though it is not needed.  (As an aside, if you add another function
similar to f, and call h with each of them, then gcc will not resolve things so
nicely at compile time and also emit code for h.)


             reply	other threads:[~2012-11-30 13:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 13:04 rohan at rohanlean dot de [this message]
2012-12-03 11:49 ` [Bug middle-end/55546] " rguenth 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-55546-4@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).