Re: [patch, nios2] Update Linux parts for new syscall ABI

[Sandra Loosemore <sandra@codesourcery.com>]

On 12/02/2013 01:37 AM, Chung-Lin Tang wrote:
> On 13/12/2 3:44 PM, Joel Brobecker wrote:
>>> Is Sandra not nios2 maintainer, or is she just not yet added to the
>>> MAINTAINERS file?
>>
>> She is not maintainer as far as I know (yet?).
>
> Then I guess something was missed during the port submission? Is nios2
> currently (technically) maintainer-less? ^^;;

FWIW, I did volunteer to be nios2 maintainer when I submitted the port. 
  I don't know if accepting the port automatically made me maintainer, 
or not.  If there is a separate process for naming maintainers, I'd be 
fine with Chung-Lin being named a co-maintainer too since he knows as 
much about this code as I do.

> nios2 support will only appear in the next 7.7 release. We're trying to
> ensure only new-ABI support appears in formal FSF releases across all
> toolchain components.
>
>> I don't have any personal interest in this, other than trying to serve
>> the interest of the potential users. If it's deemed too hard or useless
>> by the nios community, then I won't object.
>
> I can't personally judge what the community will react. However, our
> work with Altera is to move everything towards the new syscall ABI. The
> upstreamed ports of GCC and glibc will also be entirely new-ABI.

Given that nios2 GCC, glibc, and Linux kernel ports are not upstream 
yet, I think "the community" is primarily using the complete toolchains 
packaged by Altera or Mentor Graphics, which already include a GDB that 
works with the other old-ABI components packaged with those toolchains. 
  Altera wants to switch completely to the new ABI, and there will be no 
old-ABI compatibility support in future versions of GCC, glibc, or 
Linux; why is it needed in GDB?

-Sandra