Displaying 2 results from an estimated 2 matches for "pr59672".
Did you mean:
59672
2014 Jan 14
2
[LLVMdev] 16-bit x86 status update
...ode16gcc") and also adding other flags such as
-fno-unit-at-a-time to ensure that the .code16gcc really *is* the
first thing the assembler sees. We don't support that horridness,
and don't need it since clang can support '-m16'. We have also filed
http://gcc.gnu.org/PR59672 to request the same in GCC.
I have been able to build the 16-bit startup code of the Linux kernel
with .code16 and 'clang -m16', and it works fine. I had to fix PR18303,
for which David Peixotto is working on a better fix, and I had to work
around PR3997 — which some people seem to be deny...
2014 Jan 14
4
[LLVMdev] 16-bit x86 status update
...r flags such as
> > -fno-unit-at-a-time to ensure that the .code16gcc really *is* the
> > first thing the assembler sees. We don't support that horridness,
> > and don't need it since clang can support '-m16'. We have also filed
> > http://gcc.gnu.org/PR59672 to request the same in GCC.
> >
> > I have been able to build the 16-bit startup code of the Linux kernel
> > with .code16 and 'clang -m16', and it works fine. I had to fix PR18303,
> > for which David Peixotto is working on a better fix, and I had to work
> >...