From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gcc won't inline function returning struct?
Date: Thu, 01 Nov 2001 00:49:37 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805432@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805421@msgid-missing>
>If it makes function calls when the author was expecting it to do two
>computations, its performance may well be insufficient to function.
I've never heard this argument before. It does make some sense.
It does have a flaw though. If the code was originally written for IA-32, and
proven to meet timing constraints on the IA-32 host, then there is no guarantee
that it will work on an IA-64 host. The timing analysis will all have to be
redone. So perhaps the program has a valid reason for using extern inline,
but it is still non-portable, which was the point I was trying to make.
Jim
prev parent reply other threads:[~2001-11-01 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 21:39 [Linux-ia64] gcc won't inline function returning struct? Bdale Garbee
2001-10-31 22:23 ` Jim Wilson
2001-10-31 23:02 ` n0ano
2001-11-01 0:27 ` Jim Wilson
2001-11-01 0:40 ` Matthew Wilcox
2001-11-01 0:49 ` Jim Wilson [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=marc-linux-ia64-105590698805432@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.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