From: Florent DEFAY <spira.inhabitant@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: new port's validation
Date: Fri, 24 Apr 2009 12:16:00 -0000 [thread overview]
Message-ID: <8502af3c0904240516w49d8ef9br120f1ee0b0186e8c@mail.gmail.com> (raw)
Hi,
I am working on a new port.
The arch is a 16 bit machine.
The current state should enable any compilation. Libgcc is compiled.
The cc1 is working.
Now I try to validate. My method is to launch make check-gcc.
But many tests go wrong for two main reasons:
some tests need to include standard header files, but we do not need
to implement a libc
some tests are too long or use too large arrays and it is impossible
with the memory of the machine
Do you know better methods to validate GCC for such an arch?
Should we implement a libc since there is no OS?
Please, I need advice.
Regards.
Florent
next reply other threads:[~2009-04-24 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 12:16 Florent DEFAY [this message]
2009-04-24 19:35 ` Ian Lance Taylor
2009-04-27 14:44 ` Florent DEFAY
2009-04-27 21:25 ` Ian Lance Taylor
2009-04-30 22:57 ` Michael Meissner
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=8502af3c0904240516w49d8ef9br120f1ee0b0186e8c@mail.gmail.com \
--to=spira.inhabitant@gmail.com \
--cc=gcc-help@gcc.gnu.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).