From: David Edelsohn <dje@watson.ibm.com>
To: 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 21:30:38 -0500 [thread overview]
Message-ID: <200101210230.VAA37976@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from "Kevin B. Hendricks" <khendricks@ivey.uwo.ca> of "Sat, 20 Jan 2001 21:19:31 EST." <01012021193101.13943@localhost>
>>>>> "Kevin B Hendricks" writes:
Kevin> That wasn't what I asked. I asked what the process would be for making this
Kevin> decision (if it has already not been made).
Actually, it is the answer. The decision would be made by the
developers if there was a good argument for it and/or a proposed
implementation. The GCC SC might make the final decision, guided by the
public discussion. The main issue with GCC extensions is that they be
well-defined so that we avoid the repeat of problems that have occurred
with previous extensions.
What ever is proposed will not be included in GCC 3.0 because that
release has been frozen with respect to new features.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-21 2:30 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
2001-01-21 2:02 ` David Edelsohn
2001-01-21 2:19 ` Kevin B. Hendricks
2001-01-21 2:30 ` David Edelsohn [this message]
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=200101210230.VAA37976@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=andyj@mc.com \
--cc=khendricks@ivey.uwo.ca \
--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 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 NNTP newsgroup(s).