From: Joel Brobecker <brobecker@adacore.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: Chung-Lin Tang <cltang@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [patch, nios2] Update Linux parts for new syscall ABI
Date: Tue, 03 Dec 2013 03:01:00 -0000 [thread overview]
Message-ID: <20131203030101.GA3114@adacore.com> (raw)
In-Reply-To: <529CB31A.1050704@codesourcery.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
next prev parent reply other threads:[~2013-12-03 3:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 8:20 Chung-Lin Tang
2013-12-02 3:23 ` Joel Brobecker
2013-12-02 4:46 ` Chung-Lin Tang
2013-12-02 7:44 ` Joel Brobecker
2013-12-02 8:38 ` Chung-Lin Tang
2013-12-02 16:20 ` Sandra Loosemore
2013-12-03 3:01 ` Joel Brobecker [this message]
2013-12-10 6:55 ` Yao Qi
2013-12-03 3:07 ` Joel Brobecker
2013-12-20 13:16 ` Chung-Lin Tang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131203030101.GA3114@adacore.com \
--to=brobecker@adacore.com \
--cc=cltang@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=sandra@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).