public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom <madtom1999@googlemail.com>
To: Juan Perez-Sanchez <lithoxs@gmail.com>,
	linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: New GCC compiler for 8086 cpu's
Date: Wed, 14 Jun 2017 07:47:53 +0100	[thread overview]
Message-ID: <56676edf-5691-2587-34fa-533e08490dea@googlemail.com> (raw)
In-Reply-To: <CAD6VGuYYtMEhP7dEM4ftr5FHaSid-kdNQqPk7dojEU4RE2hd-A@mail.gmail.com>

On 14/06/17 01:08, Juan Perez-Sanchez wrote:
> For those interested, Mentor announced a GCC back end for 8086 family of cpu's.
> See the link:
>
> https://blogs.mentor.com/embedded/blog/2017/04/01/announcing-sourcery-codebench-lite-for-ia16/
>
> Following the links there you can reach the page for download.
> This seems to be a development based on ia16-gcc previously mentioned
> in this list, but using a newer version of GCC and all rough edges
> rounded.
>
> I used this compiler to build the ELKS kernel. The kernel produced
> appears to work fine. The compiler is very fast and produces a smaller
> kernel.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
Does it recurse? ie can you build it so it works on ELKS?

Tom


  reply	other threads:[~2017-06-14  6:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  0:08 New GCC compiler for 8086 cpu's Juan Perez-Sanchez
2017-06-14  6:47 ` Tom [this message]
2017-06-14 19:53   ` Juan Perez-Sanchez
2017-06-15 10:19 ` Edoardo
2017-06-15 22:53   ` Juan Perez-Sanchez
2017-06-16 13:33     ` David O'Shea
2017-06-16 18:57       ` Juan Perez-Sanchez
2017-06-19  3:58         ` David O'Shea
2017-06-19  6:58           ` Georg Potthast
2017-06-19  9:15             ` David O'Shea
2017-06-19 19:36           ` Juan Perez-Sanchez
2017-06-19 13:16       ` Alan Cox
2017-06-19 13:43     ` Alan Cox
2017-06-19 19:57       ` Juan Perez-Sanchez
2017-06-19 20:55         ` Alan Cox
2017-06-19 22:53           ` Juan Perez-Sanchez
2017-06-20 11:37             ` Alan Cox
2017-06-20 21:57               ` Juan Perez-Sanchez
     [not found]                 ` <CALgV52iFRay4y8dYrP0ZGnF2JQJi2h7c=QnSsDniv72azmFPbA@mail.gmail.com>
2017-06-20 22:46                   ` Fwd: " David Given

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=56676edf-5691-2587-34fa-533e08490dea@googlemail.com \
    --to=madtom1999@googlemail.com \
    --cc=linux-8086@vger.kernel.org \
    --cc=lithoxs@gmail.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