From: Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>
To: hasdi@umich.edu
Cc: amylaar@cygnus.co.uk, egcs@cygnus.com
Subject: Re: g++/i386: 4-byte inline struct return
Date: Fri, 18 Sep 1998 02:04:00 -0000 [thread overview]
Message-ID: <199809180725.JAA00544@mira.isdn.cs.tu-berlin.de> (raw)
In-Reply-To: <Pine.SOL.3.95.980917102141.1482A-100000@stargate.rs.itd.umich.edu>
> 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?
The problem is that the ABI is already defined, caller and callee will
not follow the same convention if one of them is changed now, and the
other is in a library that we have no control over.
Regards,
Martin
next prev parent reply other threads:[~1998-09-18 2:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-16 22:55 Hasdi R Hashim
1998-09-17 9:59 ` Joern Rennecke
1998-09-17 9:59 ` Hasdi R Hashim
1998-09-17 9:59 ` Joern Rennecke
1998-09-17 9:59 ` Hasdi R Hashim
1998-09-17 18:37 ` Joe Buck
1998-09-18 2:04 ` Martin von Loewis [this message]
1998-09-18 6:59 ` Hasdi R Hashim
1998-09-17 22:12 ` Martin von Loewis
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=199809180725.JAA00544@mira.isdn.cs.tu-berlin.de \
--to=martin@mira.isdn.cs.tu-berlin.de \
--cc=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=hasdi@umich.edu \
/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).