public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rafael.espindola at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58045] New: gcc 4.8 produces an undefined reference to an inline function Date: Thu, 01 Aug 2013 14:08:00 -0000 [thread overview] Message-ID: <bug-58045-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58045 Bug ID: 58045 Summary: gcc 4.8 produces an undefined reference to an inline function Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: rafael.espindola at gmail dot com CC: hubicka at gcc dot gnu.org, jason at redhat dot com Created attachment 30582 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30582&action=edit testcase This may or may not be a duplicate of bug 53808. When compiling this testcase with cc1plus llvm-ar.ii -quiet -std=c++11 -fprofile-arcs -o test.s -O2 The produced assembly has an undefined reference to _ZNK4llvm14raw_fd_ostream11current_posEv, but this function is defined inline: virtual uint64_t current_pos() const { return pos; } This causes the link to fail when building with -fvisibility-inlines-hidden and shared libraries. GCC should avoid devirtualizing or emit a copy of the callee.
next reply other threads:[~2013-08-01 14:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-01 14:08 rafael.espindola at gmail dot com [this message] 2013-09-09 8:55 ` [Bug c++/58045] " hubicka at gcc dot gnu.org 2021-07-22 18:54 ` pinskia at gcc dot gnu.org 2021-09-10 7:09 ` pinskia 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-58045-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: 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).