From: Paul Derbyshire <pderbysh@usa.net>
To: djgpp@delorie.com, egcs@egcs.cygnus.com
Subject: Code gen question
Date: Sun, 28 Feb 1999 22:53:00 -0000 [thread overview]
Message-ID: <3.0.6.32.19990212180551.00841100@pop.netaddress.com> (raw)
Message-ID: <19990228225300.1MNHsTrjPS0F24pXH8qF6ZQVhwjBVENLwvenrmBuEK0@z> (raw)
Which will cause cc1plus to generate better code?
inline int myclass::myfunc (int j) { return j*j*j; }
inline int myclass::myfunc (const int &j) { return j*j*j; }
My guess would be the latter, since the latter when inlined won't make a
copy of the argument passed. However, it might be that at high -O settings
cc1plus will spot that the first version doesn't modify j and silently
compile it like the second version.
If so, this leads me to ask: under what circumstances will the compiler be
smart enough to detect that an inline function passed an argument of a
builtin type doesn't modify it and avoid making an unnecessary copy?
This leads me to ask: when writing short inline functions, is it better for
code optimization to pass builtin data types (bool, int, double, etc.) and
pointers by value or by reference? (Yuck, passing pointers by reference,
well I'll do it if it means real speed gains in tiny inline functions that
get invoked a great deal.)
--
.*. "Clouds are not spheres, mountains are not cones, coastlines are not
-() < circles, and bark is not smooth, nor does lightning travel in a
`*' straight line." -------------------------------------------------
-- B. Mandelbrot | http://surf.to/pgd.net
_____________________ ____|________ Paul Derbyshire pderbysh@usa.net
Programmer & Humanist|ICQ: 10423848|
next reply other threads:[~1999-02-28 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-12 15:06 Paul Derbyshire [this message]
[not found] ` < 3.0.6.32.19990212180551.00841100@pop.netaddress.com >
1999-02-12 15:29 ` Joe Buck
1999-02-28 22:53 ` Joe Buck
1999-02-28 22:53 ` Paul Derbyshire
[not found] <pderbysh@usa.net's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <12>
[not found] ` <Feb>
[not found] ` <1999>
[not found] ` <15:07:44>
[not found] ` <-0800>
[not found] ` <3.0.6.32.19990212180551.00841100.cygnus.egcs@pop.netaddress.com>
1999-02-12 15:29 ` Jason Merrill
[not found] ` < u990e3kxq8.fsf@yorick.cygnus.com >
1999-02-12 17:34 ` Paul Derbyshire
[not found] ` < 3.0.6.32.19990212203311.0083e6d0@pop.netaddress.com >
1999-02-12 17:39 ` Jeffrey A Law
1999-02-28 22:53 ` Jeffrey A Law
1999-02-28 22:53 ` Paul Derbyshire
1999-02-28 22:53 ` Jason Merrill
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=3.0.6.32.19990212180551.00841100@pop.netaddress.com \
--to=pderbysh@usa.net \
--cc=djgpp@delorie.com \
--cc=egcs@egcs.cygnus.com \
/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).