public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Andrew Jenner <andrew@codesourcery.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/9] New back end ia16: 16-bit Intel x86
Date: Mon, 03 Apr 2017 15:26:00 -0000	[thread overview]
Message-ID: <da9c3e99-5d71-3783-c839-9288b94c036c@redhat.com> (raw)
In-Reply-To: <1633e4a5-dc7f-4a75-e431-9539c549cca7@codesourcery.com>

On 04/01/2017 10:47 AM, Andrew Jenner wrote:
> About 10 years ago, Rask Ingemann Lambertsen sent a patch series to add
> a 16-bit x86 (i.e. 8088, 8086, 80186 and 80286 CPUs) back end. This work
> was never committed. Recently I've been doing some work on this back
> end, and today we released a Sourcery CodeBench Lite distribution based
> on it (see
> https://blogs.mentor.com/embedded/blog/2017/04/01/announcing-sourcery-codebench-lite-for-ia16/
> ). Given this, I thought it would be a good idea to send these patches
> upstream today (though obviously if I commit these it won't be until
> we're in Stage 1 and more testing has been done on the middle-end changes).
>
> I have not been able to contact Rask Ingemann Lambertsen, but he does
> have a copyright assignment for GCC on file (dated 2006-11-16) so I do
> not believe there are any copyright assignment issues that would block
> this.
Note that with the trunk in stage4 and a release rapidly approaching, 
it's unlikely that anyone will be looking in depth at this until after 
the release branch is cut.

jeff

  reply	other threads:[~2017-04-03 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01 16:47 Andrew Jenner
2017-04-03 15:26 ` Jeff Law [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-30 14:37 Rask Ingemann Lambertsen
2007-08-09 20:28 ` Rask Ingemann Lambertsen

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=da9c3e99-5d71-3783-c839-9288b94c036c@redhat.com \
    --to=law@redhat.com \
    --cc=andrew@codesourcery.com \
    --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).