Saturday, October 01, 2005

Return value optimization

In C++, writing a function with a compound return statement like this
const Rational function (void)
{
....
return Rational (a,b); // statement 1
}

can be more efficient than

const Rational function (void)
{
....
Rational r(a,b);
return r; // statement 2
}

when used in the surrounding context such as

main()
{
Rational c = function (); // initializing c.
}

because compilers can avoid "invisible" creation and
destruction of temporaries when function returns an object
by value. This is known as "return value optimization".
In the optimized assembly code, object c is directly
initialized by statement 1. You save upto 2 temporaries (and
creation/destruction of them). One is the local object
r and other one is created and destroyed when the
function returns.

13 comments:

Anonymous said...

Ways To Make Money From a Blog
Sep 30, 2005 2:58 pm US/Eastern NEW YORK Here are three signs that you might be able to make money from a blog: 1. You have credibility in your industry.
I'm glad I ran across your blog. It's very good. I like it.

Sonny M.

I have a related site that focuses on clinical depression you may like too...It pretty much covers clinical depression related stuff.

Come and check it out if you get time :-)

Anonymous said...

Google-NASA partnership rockets Web debate
As part of Google's just-announced plan to build up 1 million square feet of offices at NASA Ames Research Center near Mountain View, Calif., the two entities will cooperate on research projects such as ...
Hey, just happened to trip across you blog when searching for car hire in london . Pretty interesting stuff, so I’ll probably stop by and check it out again.

delightfully-different said...

Terrific blog. I search the internet everytime I
get a moment to find blogs. Its better than cold iced
tea and I have to visit it one more time!
I want you to stop and compare with my 1800contacts web coupon code blog.

outa-time said...

Striking blog. I liked the site I will be back
again! Websurfing is a good way to find blogs like
yours.
Everyday of the month you need to peep my 1800contacts coupon codes blog.

lightly-blended said...

Great blog. I'm always finding blog like yours. It
got my attention and I will go to the site again!
Hey son, you need to check out my coupon codes 1800contacts blog!

car donation tax breakc said...

Unique blog my friend, I can hardly wait to vist
this site again. I just worship the site its comes
from! Believe me in my extra time I'm consistently
looking up blogs like this.
Please come by and see my 1800contacts coupon code blog.

job opportunitya said...

Irresistible blog. I look for blogs like this one
when time allows me to. I enjoyed the site and I'll
check it next time!
I hope you can look through my plastic surgery gone wrong blog.

Anonymous said...

Good insightful content... Cool use of a blog

towi said...

I am not absolutely sure, but I think, the rules for RVO are a bit wider. I think the compiler can also optimize if all "return"s directly call a constructor OR all "return"s return the same instance.
This could also be RVO'd:

Obj func()
{
__if(sunshine)
____return Obj("blue");
__else
____return Obj(42);
}

This would be, because the compiler can allocate the memory for the return value, then work through the function, and depending on which "return" call the appropriate constructor with the already allocated space.
It would not work if you mixed the two variants.
[towi@geocities.com]

Anonymous said...

wrong. both forms WILL BE optimized.

Anonymous said...

Following code calls constructor only twice.

Chk Test()
{
Chk p;
p.Set(1);

return p;

}

int main(int argc, char* argv[])
{ Chk q ;

q = Test();
}





http://vijayvcplusplus.blogspot.com/

Anonymous said...

Please stop copying codes from famous books and put them in your blog to have fame. To all readers, instead reading these blogs, please read "Efficient C++" series from Scott Mayer.

Anonymous said...

Please stop copying codes from famous books and put them in your blog to have fame. To all readers, instead reading these blogs, please read "Efficient C++" series from Scott Mayer. Most of the codes are copied from that book and if you read from book, you will get much more insight about these topics.