From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 0/9] New back end ia16: 16-bit Intel x86
Date: Thu, 09 Aug 2007 20:28:00 -0000 [thread overview]
Message-ID: <20070809202752.GM25795@sygehus.dk> (raw)
In-Reply-To: <20070730134217.GK25795@sygehus.dk>
On Mon, Jul 30, 2007 at 03:42:17PM +0200, Rask Ingemann Lambertsen wrote:
> Test results are at
> <URL:http://gcc.gnu.org/ml/gcc-testresults/2007-07/msg01175.html>. I have
> more testsuite patches coming, so the results will improve. The simulator
> setup is also rather crude at the moment and I'll post a folloup to this
> message in the next few days with more details once I tie a few loose ends.
Download these files:
http://nospamnospam.homepage.dk/gcc/download/newlib.patch
http://nospamnospam.homepage.dk/gcc/download/newlib.tar.gz
http://nospamnospam.homepage.dk/gcc/download/unix.exp
1) Create a combined tree with newlib and libgloss.
2) Apply newlib.patch.
3) Extract newlib.tar.gz.
4) Find binutils for an i386 ELF system somewhere and create links to the
binaries as ia16-unknown-elf-{as,ld,ar,ranlib,strip,nm}.
5) Configure --target=ia16-unknown-elf and build as with any other target.
There's a quick and dirty simulator for Linux/ia32 systems included. It's
only a wrapper around the vm86() system call and provides none of the fancy
stuff, just arguments and return value. Use unix.exp above when running the
testsuite. Note: It needs to be called unix.exp.
--
Rask Ingemann Lambertsen
next prev parent reply other threads:[~2007-08-09 20:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 14:37 Rask Ingemann Lambertsen
2007-07-30 14:56 ` [PATCH 1/9] New target " Rask Ingemann Lambertsen
2007-07-30 15:08 ` [PATCH 2/9] Fix reloads_unique_chain_p() missing a conflict Rask Ingemann Lambertsen
2007-08-10 8:47 ` PING " Rask Ingemann Lambertsen
2007-08-21 11:23 ` ping^2 " Rask Ingemann Lambertsen
2007-08-30 8:28 ` ping^3 [PATCH] " Rask Ingemann Lambertsen
2007-07-30 16:10 ` [PATCH 3/9] reload_reg_free(): Rask Ingemann Lambertsen
2007-08-10 8:49 ` PING [PATCH 3/9] reload_reg_free(): don't clobber inherited registers Rask Ingemann Lambertsen
2007-08-21 11:24 ` ping^2 " Rask Ingemann Lambertsen
2007-08-30 8:50 ` ping^3 [PATCH] " Rask Ingemann Lambertsen
2007-07-30 16:35 ` [PATCH 4/9] Subreg handling in reload_inner_reg_of_subreg() and push_reload() Rask Ingemann Lambertsen
2007-08-10 8:49 ` PING " Rask Ingemann Lambertsen
2007-08-21 11:29 ` ping^2 " Rask Ingemann Lambertsen
2007-08-30 8:50 ` ping^3 [PATCH] " Rask Ingemann Lambertsen
2007-07-30 17:22 ` [PATCH 5/9] Libgcc bits and the back end itself Rask Ingemann Lambertsen
2007-07-30 19:08 ` [PATCH 6/9] Documentation for the ia16 back end Rask Ingemann Lambertsen
2007-08-11 19:01 ` Joseph S. Myers
2007-07-30 19:10 ` [PATCH 7/9][wwwdocs] Mention ia16 in backends.html Rask Ingemann Lambertsen
2007-07-30 22:48 ` Gerald Pfeifer
2007-07-30 19:36 ` [PATCH 8/9] Vectorizer testsuite fixes Rask Ingemann Lambertsen
2007-07-30 20:40 ` Janis Johnson
2007-07-30 20:08 ` [PATCH 9/9] Skip or xfail some tests on ia16 Rask Ingemann Lambertsen
2007-07-30 20:51 ` Janis Johnson
2007-08-09 20:28 ` Rask Ingemann Lambertsen [this message]
2017-04-01 16:47 [PATCH 0/9] New back end ia16: 16-bit Intel x86 Andrew Jenner
2017-04-03 15:26 ` Jeff 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=20070809202752.GM25795@sygehus.dk \
--to=rask@sygehus.dk \
--cc=gcc-patches@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).