public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Greg Galloway <gregg@eoeml.gtri.gatech.edu>
Cc: egcs@cygnus.com
Subject: Re: EGCS-970929 and GNAT-3.10p?
Date: Wed, 08 Oct 1997 21:19:00 -0000	[thread overview]
Message-ID: <10334.876363803@hurl.cygnus.com> (raw)
In-Reply-To: <199710082117.RAA06460@nospokes.gtri.gatech.edu>

  In message < 199710082117.RAA06460@nospokes.gtri.gatech.edu >you write:
  > 
  > Is it possible to (re)build GNAT-3.10p with EGCS-970929 instead of
  > GCC-2.7.2.1?
We don't know.  Nobody's actually tried it...  Well, maybe one person,
but I don't know what version of GNAT and EGCS he was working with or
how much time he spent on it.

  > The gnat-3.10p-src/gcc-2721.dif seems to contain patches
  > that have already been applied to EGCS.
Most, if not all of those patches should be in EGCS.

However, other changes made since gcc-2.7 may prevent GNAT from building.

  > not checked every last one of them.  I would like to get the benefits
  > of EGCS with respect to C++ and FORTRAN without loosing Ada.  I'm also
  > trying to build using the gcc/gnat binaries from cs.nyu.edu:/pub/gnat.
Folding in GNAT is one of our long term goals; anything you can do to help
us reach that goal would be greatly appreciated.

I'll help as much as I can :-)

  > I'm trying to build for mips-irix6.3, mips-irix5.3, rs6k-aix3.2,
  > alpha-osf3.2, sparc-solaris2.5, and sparc-sunos4.1.3.
I'd pick one platform and stick with it until you can get something that
works.

  > I've got a segmentation violation from collect2 during the link for cc1
  > for mips-irix5.3, and a misaligned data error compiling gmon-sol2.c
  > for sparc-solaris2.5.
There's been a report of some problems with mips-sgi-irix5.2 which
occur due to -lmalloc.  I don't know if those might be related to your
irix5.3 problems.

As for the misaligned data error -- can you provide some more details?
What program got the misaligned data error?

jeff

  reply	other threads:[~1997-10-08 21:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-08 14:14 Greg Galloway
1997-10-08 21:19 ` Jeffrey A Law [this message]
1997-10-09  9:26   ` Joel Sherrill
1997-10-09 16:31     ` Jim Wilson
1997-10-15 21:43     ` Jeffrey A Law
1997-10-16  2:35       ` Klaus Kaempf
1997-10-16  8:31         ` Jeffrey A Law
1997-10-16 12:53       ` Jim Wilson
1997-10-16 15:19         ` Jeffrey A Law
1997-10-16 15:19         ` Joel Sherrill
1997-10-16 15:19       ` Joel Sherrill
1997-10-16 15:19         ` Jeffrey A Law
1997-10-16 21:51           ` Richard Henderson
1997-10-16 23:09             ` egcs-971016 Oleg Krivosheev
1997-10-17 14:36               ` egcs-971016 Jeffrey A Law
1997-10-17  5:26             ` EGCS-970929 and GNAT-3.10p? Joel Sherrill
1997-10-17 15:05               ` Toon Moene
1997-10-18  8:45                 ` Joel Sherrill
1997-10-23 13:54                   ` Toon Moene
1997-10-23 12:49                     ` Joel Sherrill
1997-10-09 16:12   ` Jim Wilson
1997-10-09  9:26 Greg Galloway
1997-10-09 16:12 ` Jim Wilson
1997-10-15 20:16   ` Jeffrey A Law
1997-10-16 12:50     ` Jim Wilson
1997-10-16 12:50 Greg Galloway
1997-10-16 12:53 ` Jeffrey A Law

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=10334.876363803@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=gregg@eoeml.gtri.gatech.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).