public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: Robert Dewar <dewar@gnat.com>
Cc: willy@debian.org, gcc@gcc.gnu.org
Subject: Re: What CPU ports should have working Ada?
Date: Mon, 03 Feb 2003 14:32:00 -0000	[thread overview]
Message-ID: <3E3E7D70.F9C2C037@OARcorp.com> (raw)
In-Reply-To: <20030203124343.8BA92F28E4@nile.gnat.com>



Robert Dewar wrote:
> 
> This is a hard question to answer, since it depends on what you mean by
> working. For us, working means passing our entire test suite, and in those
> terms, none of the Debian ports are close to doing this yet. We are finally
> getting to the point where for some selected targets, we are getting
> clean runs, but there is still quite a way to go.

I was wanting to get a list of the CPU families that had > 0 support for
Ada so would know which ones even had a possibility of being worth
attempting
to use on GNAT/RTEMS.  The behavior of RTEMS is a known and consistent
quantity across all ports.  Thus if GNAT is stable enough to compile the
run-time 
for a particular CPU family, then we should get the same ACATS test
results
across all RTEMS ports.  I was hoping this would help with the testing
since
the OS wouldn't be as much of a factor in the problems.

I did not expect 100% passing at this time on the gcc 3.x source base. 
Only
similar test results if GNAT compiled for a particular CPU familiy at
all.

As it stands, we are now providing RPMs with GNAT for every CPU family
(except hppa) that has a "working" GNAT and RTEMS port -- sparc,
powerpc, 
mips, and i386.  The big ones to add next are the m68k and ARM. And
as of the 3.3 branch, the m68k is supposed to have the exception
handling
stuff in place.

Thanks, Dr. Dewar.

--joel

  reply	other threads:[~2003-02-03 14:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 12:43 Robert Dewar
2003-02-03 14:32 ` Joel Sherrill [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-03 11:58 Matthew Wilcox
2003-01-31 15:48 Joel Sherrill
2003-01-31 16:00 ` Andreas Schwab
2003-01-31 16:51   ` Joel Sherrill
2003-01-31 17:11     ` Andreas Schwab
2003-02-02 14:34 ` Marc Espie

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=3E3E7D70.F9C2C037@OARcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=willy@debian.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 read-only IMAP folder(s) and NNTP newsgroup(s).