public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "u1049321969 at caramail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99900] feature request: 16-bit x86 C compiler / support compilation of (VirtualBox) BIOS
Date: Thu, 08 Apr 2021 14:44:57 +0000	[thread overview]
Message-ID: <bug-99900-4-WAicBYqaaF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99900-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99900

--- Comment #6 from tk <u1049321969 at caramail dot com> ---
Hello Andrew,

> A bug bounty might be useful here since I highly doubt this will be done 
> otherwise.

The gcc-ia16 port is working, but internals-wise, some parts of the IA-16
patches are still rather hacky --- some of the changes affect the
machine-independent middle-end in not-so-elegant ways, or depend on
undocumented (and unreliable) properties in the middle-end.

So I guess it might still be useful to have some sort of bounty(s), if this
means someone could help rethink the changes and reduce technical debt.

Thank you!

  parent reply	other threads:[~2021-04-08 14:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03 20:14 [Bug c/99900] New: " adrelanos at whonix dot org
2021-04-03 20:29 ` [Bug target/99900] " pinskia at gcc dot gnu.org
2021-04-04 10:58 ` adrelanos at whonix dot org
2021-04-06 23:11 ` joseph at codesourcery dot com
2021-04-07  5:39 ` egallager at gcc dot gnu.org
2021-04-08 14:37 ` u1049321969 at caramail dot com
2021-04-08 14:44 ` u1049321969 at caramail dot com [this message]
2021-04-08 18:01 ` u1049321969 at caramail dot com
2021-04-09 14:34 ` u1049321969 at caramail dot com

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=bug-99900-4-WAicBYqaaF@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).