public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: martin.gerbershagen@icn.siemens.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/3698: improper handling of an extern declared inline function
Date: Mon, 16 Jul 2001 01:46:00 -0000	[thread overview]
Message-ID: <20010716083605.1206.qmail@sourceware.cygnus.com> (raw)

>Number:         3698
>Category:       c++
>Synopsis:       improper handling of an extern declared inline function
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 16 01:46:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Martin Gerbershagen
>Release:        g++-3.0
>Organization:
>Environment:
sparc-sun-solaris2.6
>Description:
If a function, that has been defined as a global inline
function, is declared extern in a local scope, a reference
to an external function is emitted in the object code and
not the substitution of the inline function. If the 
extern declaration is moved to the global scope the inline
substitution works correctly. The generated code creates
link errors later on.

g++ b.C
/var/tmp/ccaFlZr0.o: In function `main':
/var/tmp/ccaFlZr0.o(.text+0x8): undefined reference to `OHashKey(X const&)'
collect2: ld returned 1 exit status

>How-To-Repeat:
class X {
public:
   int i;
};

inline const int& OHashKey(const X& x) {
   return x.i;
}

int main() {
   extern const int& OHashKey(const X& x);
   X x;
   return OHashKey(x);
}
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-07-16  1:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16  1:46 martin.gerbershagen [this message]
2002-10-21 17:49 zack

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=20010716083605.1206.qmail@sourceware.cygnus.com \
    --to=martin.gerbershagen@icn.siemens.de \
    --cc=gcc-gnats@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).