Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chung-Lin Tang <cltang@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>, Sandra Loosemore <sandra@codesourcery.com>
Subject: Re: [patch, nios2] Update Linux parts for new syscall ABI
Date: Mon, 02 Dec 2013 08:38:00 -0000	[thread overview]
Message-ID: <529C46BA.8050403@codesourcery.com> (raw)
In-Reply-To: <20131202074423.GS3114@adacore.com>

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? ^^;;

>>>> 2013-12-01  Chung-Lin Tang  <cltang@codesourcery.com>
>>>>
>>>>         gdb/
>>>>         * nios2-linux-tdep.c (nios2_linux_sigreturn_init): Remove.
>>>>         (nios2_linux_sigreturn_tramp_frame): Remove.
>>>>         (nios2_linux_rt_sigreturn_tramp_frame): Update rt_sigreturn syscall
>>>>         number.
>>>>         (nios2_linux_syscall_next_pc): Likewise. Remove sigreturn case.
>>>>         (nios2_linux_init_abi):
>>>>         Remove registration of nios2_linux_sigreturn_tramp_frame.
>>>
>>> My concern with your patch is that it seems to eliminate support for
>>> the previous syscall ABI, which means a break in compatibility. Unless
>>> we really have no other choice, I don't think we would want that.
>>
>> This is a coordinated change, Altera will be using the new syscall ABI
>> when they upstream the kernel port.
> 
> I understand that. But is it conceivable that someone might be wanting
> to use the new GDB while still running on the old kernel, with the old
> software convention? How about the transition period? A break in
> compatibility is very unfriendly for the average user, and needs
> to be carefully considered.

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.

Thanks,
Chung-Lin


  reply	other threads:[~2013-12-02  8:38 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 [this message]
2013-12-02 16:20         ` Sandra Loosemore
2013-12-03  3:01           ` Joel Brobecker
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=529C46BA.8050403@codesourcery.com \
    --to=cltang@codesourcery.com \
    --cc=brobecker@adacore.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