From: Jeff Law <law@redhat.com>
To: Andrew Jenner <andrew@codesourcery.com>,
Dennis Luehring <dl.soluz@gmx.net>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: current state of gcc-ia16?
Date: Mon, 11 Jun 2018 19:19:00 -0000 [thread overview]
Message-ID: <cd770974-59c3-24d3-2032-7e12e2e6db93@redhat.com> (raw)
In-Reply-To: <a0265808-4795-8c44-e2d1-7a545ec69ce8@codesourcery.com>
On 06/08/2018 06:05 AM, Andrew Jenner wrote:
> On 08/06/2018 12:43, Dennis Luehring wrote:
>>>> is the patch already integrated into mainline?
>>> No, it's not.
>>
>> will that ever happen?
>
> Hard to say. There's no reason in principle why it couldn't happen, but
> there's not a big demand for it, so it would require someone taking the
> time and trouble to do it. It's not trivial, though - the current
> implementation has some middle-end changes which would need thinking
> through and doing properly to avoid polluting that code with ia16-isms.
>
> I might update it and have another try at upstreaming it at some point
> if nobody else does it first, but I have too much else going on at the
> moment so it would likely be a year or two (maybe more) before I get to it.
Time is by far the biggest concern for the ia16 backend. THere's just a
mountain of higher priority stuff right now. It doesn't help that I
keep getting dragged into other stuff :(
jeff
prev parent reply other threads:[~2018-06-11 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 10:59 Dennis Luehring
2018-06-08 11:43 ` Andrew Jenner
2018-06-08 12:06 ` Dennis Luehring
2018-06-08 13:22 ` Andrew Jenner
2018-06-11 19:19 ` Jeff Law [this message]
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=cd770974-59c3-24d3-2032-7e12e2e6db93@redhat.com \
--to=law@redhat.com \
--cc=andrew@codesourcery.com \
--cc=dl.soluz@gmx.net \
--cc=gcc@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).