This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: g++/i386: 4-byte inline struct return


On Thu, 17 Sep 1998, Joern Rennecke wrote:
> We can't do this for non-inline static functions - nor the non-inline
> expansion of an inline static function - if the choice in general is
> -fpcc-struct-return .  We don't know if the address of the function is
> taken before we have compilde the entire file.

Ok. non-inline statics can wait, unless somebody insists on being
adventurous in -O3. For regular inlines, I don't see any reason why you
want to return in memory (at least in most cases I've seen). It really
pains me to see redundant stores all over the code when using my
fixed-point arithmetic class (maybe I didn't implement it well enough :(. 

Hasdi




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]