MK_ARM_EABI to retire in current

[John-Mark Gurney]

Adrian Chadd wrote this message on Mon, May 19, 2014 at 09:50 -0700:
> isn't eabi on the xscale still broken?

I don't think it's EABI that is broken, though I will admit that I
haven't ever tried to boot AVILA w/ OABI (that I can remember)...

I have managed to decode the vm_page as requested and provided the
info to various parties, but no one has looked at it, or at least
come up with request for additional data...  I would like to see it
fixed, but w/o support to figure out why a page is being wired when it
shouldn't, it isn't going to happen...

> On 19 May 2014 08:40, Warner Losh <imp at bsdimp.com> wrote:
> > Greetings,
> >
> > MK_ARM_EABI is going to die in current. It is the default for all platforms currently. I???m eliminating it as a build option. It must die because it invisibly (to uname) effects the ABI.
> >
> > So, to that end, I see two options:
> >
> > (1) Retire and remove oabi support.
> > (2) Retain oabi support, but change its name to armo and armoeb.
> >
> > The rough consensus of arm developers I???ve polled now, and in the past, is that we just let oabi support die now that EABI support is working for everybody.
> >
> > Before I pull the trigger on this, however, I must ask if anybody has a problem with my doing option (1), and if so, what keeps you using oabi.
> >
> > Comments?

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."