This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch, nios2] Update Linux parts for new syscall ABI
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Sandra Loosemore <sandra at codesourcery dot com>
- Cc: Chung-Lin Tang <cltang at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Tue, 3 Dec 2013 07:01:01 +0400
- Subject: Re: [patch, nios2] Update Linux parts for new syscall ABI
- Authentication-results: sourceware.org; auth=none
- References: <529AF143 dot 9060704 at codesourcery dot com> <20131202032333 dot GN3114 at adacore dot com> <529C107E dot 10308 at codesourcery dot com> <20131202074423 dot GS3114 at adacore dot com> <529C46BA dot 8050403 at codesourcery dot com> <529CB31A dot 1050704 at codesourcery dot com>
> 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?
I wasn't saying that this was needed for GDB, just that it usually
is very unfriendly to break compatibility if users (what I called
the "community" for lack of better words) are allowed to mix and
match the various elements of the system. When I see such a deliberate
break, I always prefer to make sure that this is OK, so I asked.
In your case, you are explaining why this is not a problem, and
I see your point. But it is important, IMO, to have that explained,
if only for the public record.
--
Joel