From: Jeffrey A Law <law@cygnus.com>
To: Mark Hatle <fray@eel2.cs.mankato.msus.edu>
Cc: egcs@cygnus.com
Subject: Re: Inline functions
Date: Tue, 12 May 1998 18:04:00 -0000 [thread overview]
Message-ID: <1428.895015697@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.95.980512121158.12719B-100000@EEL2.cs.mankato.msus.edu>
In message < Pine.LNX.3.95.980512121158.12719B-100000@EEL2.cs.mankato.msus.edu
> How can I compile selected files in the Linux server without optimization
> and still have the inline functions inline? (or at least compile as
> regular functions in that object file?)
inlining is only performed when optimizing.
You need to declare the functions as static inline like this example
so that you'll get a copy of the function when not optimizing:
int z;
static inline x (int y) { z = y; }
foo()
{
x (5);
}
next prev parent reply other threads:[~1998-05-12 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-12 12:36 Mark Hatle
1998-05-12 15:33 ` Richard Henderson
1998-05-12 18:04 ` Jeffrey A Law [this message]
1998-05-12 18:04 ` Joe Buck
1998-05-13 1:47 ` Hans Zuidam
1998-05-13 1:58 ` Akim Demaille
1998-05-13 10:04 Michael Meissner
1998-05-14 1:04 ` Hans Zuidam
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=1428.895015697@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=fray@eel2.cs.mankato.msus.edu \
/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).