Re: Efficiency of returning big objects

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Mon, 25 Sep 2006 14:14:44 +0200, Alex R. Mosteo wrote:

> I had a concern over the efficiency of returning big (tagged) types, since I
> like to store them in indefinite collections (a la Object'Class) instead of
> storing pointers to them. It is said that, as tagged types are passed by
> reference, they are always efficiently passed around. However, when you
> are /returning/ and not calling, I had my doubts, so I have made this
> simple testcase (see at bottom).

Same with arrays - when returning a slice of a non-local string, GNAT
copies it. It does this even when the callee is inlined.
 
> It has been compiled with just gnatmake -O3. It reveals that a copy is
> created in the stack for returning every time. I was hoping that, as long
> as the type were used as a constant, a reference would be returned and
> passed around. This would be very interesting in collections, since we
> could do, for example:
> 
> Some_Map.Element (Key).Method_Or_Member
> 
> without efficiency penalties.
> 
> Now, in C++ I would force this behavior explicitly returning references (I
> guess this is the usual practice, but I'm not sure). In Ada, I have no idea
> how to match this efficient behavior.

In Ada 2006 an equivalent would be an anonymous access type of the result.
As ugly as C++, but works.

> So, what do you think? Is there some error in my reasoning or testbed? Is
> this a particular shortcoming of this compiler (gnat gpl 2006), or I'm
> overlooking something that makes this very non-trivial to implement?

You mean, checking if the scope of the name of the function result is in
the scope of the object returned? It is a global + temporal variables
optimizations, AFAIK. And the callee should be inlined. [ However, I
suppose, GNAT would make a copy even if your Create were inlined. ]

In the specific case:

   function Get (X : Container_Type; ...) return Element_Type;

the compiler could know that the result is from X. But it were still
possible something like:

   Get (Read_Container_From_File, First_Element); -- Shall copy

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de