All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: David Edelsohn <dje@watson.ibm.com>, khendricks@ivey.uwo.ca
Cc: Andy Johnson <andyj@mc.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Issue with small struct return values
Date: Sat, 20 Jan 2001 20:52:39 -0500	[thread overview]
Message-ID: <01012020523900.13943@localhost> (raw)
In-Reply-To: <200101210041.TAA25654@mal-ach.watson.ibm.com>


Hi David,

> 	Proposing an extension to GCC is a lot more difficult than having
> GCC follow the ABI as written.

Whose decision will this be?  Is this going to be a community based decision
or will gcc decide to do this unlaterally with or without the community's
support?

What voice should the currently shipping distributions have in this?

I saw no discussion on gcc-bugs about this issue (and was not privy to your
and Geoff's previuous discussion with Andy about this issue).

That is why I responded to Andy in the first place.

What process, if any exists for this decision to be made?

I assume you wanted a community based decision since you asked Andy to cc
this to the linuxppc dev list.

Also, on a more technical note, how many <= 8 byte structures are there in
actual use anyway?  I would guess that most uninos are less than or eqaul to
8 bytes and so returning unions would change.  So according to the abi, would
we would passing a union in to a function via a pointer but returning one in
registers?

Kevin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-01-21  1:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19 22:14 Issue with small struct return values Andy Johnson
2001-01-20 14:43 ` Kevin B. Hendricks
2001-01-20 21:37   ` David Edelsohn
2001-01-21  0:04     ` Kevin B. Hendricks
2001-01-21  0:16     ` Kevin B. Hendricks
2001-01-21  0:41       ` David Edelsohn
2001-01-21  1:52         ` Kevin B. Hendricks [this message]
2001-01-21  2:02           ` David Edelsohn
2001-01-21  2:19             ` Kevin B. Hendricks
2001-01-21  2:30               ` David Edelsohn
2001-01-21  2:44                 ` Kevin B. Hendricks
2001-01-21  2:45                   ` David Edelsohn
2001-01-21  2:54                     ` Kevin B. Hendricks
2001-01-21  3:31                       ` David Edelsohn
2001-01-21  0:44     ` Brad Parker
2001-01-21  0:58       ` David Edelsohn

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=01012020523900.13943@localhost \
    --to=khendricks@ivey.uwo.ca \
    --cc=andyj@mc.com \
    --cc=dje@watson.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.