[Bug target/99900] feature request: 16-bit x86 C compiler / support compilation of (VirtualBox) BIOS

2021-04-09 Thread u1049321969 at caramail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99900

--- Comment #8 from tk  ---
Hello Patrick,

> Can you or anyone guestimate / speculate how big a bounty in USD value would
> be required to get this ticket implemented in gcc as well as getting a patch
> merged at VirtualBox starting to use this?

Offhand, I would guess that the effort is at least comparable to other efforts
to modernize GCC internals, e.g.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 , so a comparable bounty is
likely needed.

But perhaps someone who is more knowledgeable about GCC internals can provide a
better estimate.

Thank you!

[Bug target/99900] feature request: 16-bit x86 C compiler / support compilation of (VirtualBox) BIOS

2021-04-08 Thread u1049321969 at caramail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99900

--- Comment #7 from tk  ---
Hello Andrew,

Incidentally, the patches for binutils-ia16
(https://github.com/tkchia/binutils-ia16) to support IA-16 relocations
(https://github.com/tkchia/build-ia16/blob/master/elf16-writeup.md), could
perhaps also benefit from a rethink.

Thank you!

[Bug target/99900] feature request: 16-bit x86 C compiler / support compilation of (VirtualBox) BIOS

2021-04-08 Thread u1049321969 at caramail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99900

--- Comment #6 from tk  ---
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!

[Bug target/99900] feature request: 16-bit x86 C compiler / support compilation of (VirtualBox) BIOS

2021-04-08 Thread u1049321969 at caramail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99900

tk  changed:

   What|Removed |Added

 CC||u1049321969 at caramail dot com

--- Comment #5 from tk  ---
Hello all,

> I've no idea whether the (not merged) ia16 port can do this, or whether 
> the person currently maintaining a version of that port for GCC 6 is 
> covered by an FSF copyright assignment.

I am the maintainer behind the https://github.com/tkchia/gcc-ia16 fork.

Yes, I have done the copyright assignments for my IA-16 patches for GCC (in
2017) and also for Binutils (in 2018).  I believe that the previous developers,
Mr. Lambertsen and Mr. Jenner, have also made the needed copyright assignments.

The current gcc-ia16 code can produce code to run on an 8086, 80186, or 80286
machine, and also has support for far pointers --- including far function
pointers.  The texinfo documentation has been updated to lay out the features
that the IA-16 port has.

Thank you!

[Bug target/99900] feature request: 16-bit x86 C compiler / support compilation of (VirtualBox) BIOS

2021-04-06 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99900

Eric Gallager  changed:

   What|Removed |Added

 CC||andrewjenner at gcc dot 
gnu.org,
   ||dl.soluz at gmx dot net,
   ||egallager at gcc dot gnu.org,
   ||law at gcc dot gnu.org,
   ||rask at gcc dot gnu.org

--- Comment #4 from Eric Gallager  ---
(In reply to jos...@codesourcery.com from comment #3)
> I've no idea whether the (not merged) ia16 port can do this, or whether 
> the person currently maintaining a version of that port for GCC 6 is 
> covered by an FSF copyright assignment.
> 
> https://gcc.gnu.org/legacy-ml/gcc-patches/2017-04/msg9.html
> https://gcc.gnu.org/legacy-ml/gcc/2018-06/msg00103.html
> https://github.com/tkchia/gcc-ia16

cc-ing people from these threads to see if they can help fill us in here

[Bug target/99900] feature request: 16-bit x86 C compiler / support compilation of (VirtualBox) BIOS

2021-04-06 Thread joseph at codesourcery dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99900

--- Comment #3 from joseph at codesourcery dot com  ---
I've no idea whether the (not merged) ia16 port can do this, or whether 
the person currently maintaining a version of that port for GCC 6 is 
covered by an FSF copyright assignment.

https://gcc.gnu.org/legacy-ml/gcc-patches/2017-04/msg9.html
https://gcc.gnu.org/legacy-ml/gcc/2018-06/msg00103.html
https://github.com/tkchia/gcc-ia16

[Bug target/99900] feature request: 16-bit x86 C compiler / support compilation of (VirtualBox) BIOS

2021-04-04 Thread adrelanos at whonix dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99900

--- Comment #2 from Patrick Schleizer  ---
Can you or anyone guestimate / speculate how big a bounty in USD value would be
required to get this ticket implemented in gcc as well as getting a patch
merged at VirtualBox starting to use this?

[Bug target/99900] feature request: 16-bit x86 C compiler / support compilation of (VirtualBox) BIOS

2021-04-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99900

Andrew Pinski  changed:

   What|Removed |Added

   Severity|normal  |enhancement

--- Comment #1 from Andrew Pinski  ---
> Could you please develop a 16-bit x86 C compiler that supports compilation of
> VirtualBox BIOS / any BIOS?

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