This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: g++/i386: 4-byte inline struct return
- To: hasdi at umich dot edu (Hasdi R Hashim)
- Subject: Re: g++/i386: 4-byte inline struct return
- From: Joern Rennecke <amylaar at cygnus dot co dot uk>
- Date: Thu, 17 Sep 1998 16:05:40 +0100 (BST)
- Cc: amylaar at cygnus dot co dot uk, egcs at cygnus dot com
> I'll try this when I get back home. I think gcc should return struct
> values in registers anyway (ignoring -fpcc-struct-return) if the caller
> and callee can follow the same struct-return convention (i.e. inline and
> static functions). Is there a fallacy in my thinking? I hope somebody more
> experience can tell me if this is easy to 'fix' in egcs.
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.