linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@cygnus.com>
To: jeramy <jsmith@ixl.com>,
	"linuxppc-dev@lists.linuxppc.org"
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: EGCS 1.1.1 FYI
Date: Mon, 7 Dec 1998 11:12:26 -0500	[thread overview]
Message-ID: <19981207111226.A2909@tiktok.cygnus.com> (raw)
In-Reply-To: <366A3B16.48093C74@ixl.com>; from jeramy on Sun, Dec 06, 1998 at 02:06:46AM -0600


On Sun, Dec 06, 1998 at 02:06:46AM -0600, jeramy wrote:
> 
> Cygnus released 1.1.1 on Dec. 1 with the following PPC specific
> improvements.

Note, while we host the egcs machines (and provide a number of compiler
hackers), EGCS != Cygnus.  EGCS is netwide and has people from many different
organizations (including most of the developers from the FSF GCC, and many more
developers that were never part of the FSF).

> Fixed PPC/RS6000 LEGITIMIZE_ADDRESS macro and bug in conversion from
> unsigned ints to double precision floats. 
> Fixed handling of long longs for varargs/stdarg functions on the ppc. 

Note, this means any code that passes long long should have both the caller and
callee recompiled with the same compiler.

> Fixed code generation problems with gpr<->fpr copies for 64bit ppc. 

That doesn't affect PowerPC Linux right now, since the only 64-bit ppc target
is AIX based (there are a number of issues like gas/ld support, and machine
availability before it will matter to Linux/PPC).

> Makes sure target libraries build with -fPIC for PPC targets.
> 
> Good to see this much platform specific progress in a x.x.1 release. :)

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  reply	other threads:[~1998-12-07 16:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-06  8:06 EGCS 1.1.1 FYI jeramy
1998-12-07 16:12 ` Michael Meissner [this message]
     [not found] <schinder@pobox.com>
1998-12-08  2:51 ` Paul J. Schinder
1998-12-07 15:10   ` David Edelsohn
1998-12-07 22:22     ` Ralf Weidemann
1998-12-08  1:05       ` Michael Meissner
1998-12-08  6:17         ` Elgin Lee
1998-12-08 11:38         ` Gary Thomas
1998-12-08  4:28       ` hagopiar
1998-12-08 10:42         ` David T. McWherter
1998-12-08  6:59       ` Daniel Jacobowitz
     [not found] <nester@nester.dyn.ml.org>
     [not found] ` <Pine.LNX.3.96.981208202419.4464D-100000@zero>
1998-12-09  5:22   ` Elgin Lee

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=19981207111226.A2909@tiktok.cygnus.com \
    --to=meissner@cygnus.com \
    --cc=jsmith@ixl.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).