From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>,
egcs%bugs@cygnus.com
Subject: Re: inline functions not getting internal linkage in x86 without optimization
Date: Sat, 27 Jun 1998 22:14:00 -0000 [thread overview]
Message-ID: <orogvekxmk.fsf@iguacu.dcc.unicamp.br> (raw)
In-Reply-To: <9806262245.AA30672@rios1.watson.ibm.com>
David Edelsohn <dje@watson.ibm.com> writes:
> Are explicitly declared *inline* functions no longer considered
> local to the translation unit in whatever equivalent wording now
> exists?
In C++, declaring a function as inline does not affect its linkage, so
a non-member inline function is extern unless explicitly declared as
static.
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil
prev parent reply other threads:[~1998-06-27 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-26 17:02 David Edelsohn
1998-06-27 22:14 ` Alexandre Oliva [this message]
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=orogvekxmk.fsf@iguacu.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=dje@watson.ibm.com \
--cc=egcs%bugs@cygnus.com \
--cc=martin@mira.isdn.cs.tu-berlin.de \
/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).