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 21:44:41 -0500 [thread overview]
Message-ID: <01012021444103.13943@localhost> (raw)
In-Reply-To: <200101210230.VAA37976@mal-ach.watson.ibm.com>
Hi,
Forgive my stupidity here. Exactly what are you referring to as the
extension / new feature. Do developers need to propse an extension to keep
the status quo or does Andy/you/IBM need to propose something to get the
change in.
> What ever is proposed will not be included in GCC 3.0 because that
> release has been frozen with respect to new features.
Please don't get me wrong. I am not against the change. I would like access
to as much ppc based commercial software as possible (it would be nice if IBM
released their JDK for PPC Linux with your nice JIT) and put me out of
business. Apple will never release the Hotspot source to PPC Linux (I have
asked) and I hate re-inventing the wheel (and I can't read x86 assembler to
boot! so porting Hotspot will be a long term project for me at best).
I just want to understand the process of making this change to make sure we
don't create more hardship (financial and otherwise) for the few ppc linux
distributions out there as it is. I think the timing of the change would be
important for YellowDogLinux, LinuxPPC, Debian, and SuSE (forgive me if I
left anyone out) to have a say in.
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-21 2:44 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
2001-01-21 2:44 ` Kevin B. Hendricks [this message]
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=01012021444103.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 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).