From: Joel Sherrill <joel@OARcorp.com>
To: egcs@cygnus.com
Subject: Re: GCC Projects?
Date: Sun, 17 Aug 1997 21:48:08 -0000 [thread overview]
Message-ID: <m0x0CEL-0004ecC@ocean.lucon.org> (raw)
Message-ID: <19970817214808.L7YyRnnqziaSz1sGZrLB61xfWw0cJMp6S8oEb7fYuf4@z> (raw)
In-Reply-To: 5225.871844963@hurl.cygnus.com
On Sun, 17 Aug 1997, Jeffrey A Law wrote:
> > I see that there are two main unfinished projects in the egcs
> > source tree: pre-compiled include files and bytecode generation.
> > Is anyone working on one of these?
> Nobody is working on these as far as I know. Lots of other stuff
> is probably more important -- cpplib, lots of optimization work,
> fold in ada & pascal front ends, packaging & release issues, docs,
> etc etc.
I would like to put a plug in for architectural simulators here. There
are a number of targets --especially embedded ones -- which are difficult
and/or time-consuming to test. Of the RTEMS configurations (about 8
different ones), I can only do automated tests on 2 of them (powerpc and
sparc). The others I can only verify that they can successfully build a
full toolchain and support libraries. Periodically, I run code on actual
target boards.
Long term, if the testing of egcs (and other support libraries) is to be
full and complete, we really need to find/develop good simulators for a
handful of cpus.
--joel
Joel Sherrill Sr. Computer Scientist
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (205) 722-9985
next reply other threads:[~1997-08-17 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-17 21:48 H.J. Lu [this message]
1997-08-17 21:48 ` Joel Sherrill
1997-08-17 21:48 ` A patch for configure.in Jeffrey A Law
1997-08-18 5:12 An autoconf patch Doug Evans
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=m0x0CEL-0004ecC@ocean.lucon.org \
--to=joel@oarcorp.com \
--cc=egcs@cygnus.com \
/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).