From: Wei-cheng Wang <cole945@gmail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/5] Code for nds32 target
Date: Tue, 09 Jul 2013 16:18:00 -0000 [thread overview]
Message-ID: <51DC37DD.9030709@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1307082343130.7307@digraph.polyomino.org.uk>
On 7/9/2013 7:58 AM, Joseph S. Myers wrote:
> I advise reviewing this whole comment, and the Linux port in general, for
> whether it is still current.
>
> I don't see the kernel port as of Linux 3.10, and Linux kernel policy as I
> understand it is that new architectures are expected to use the generic
> syscall interface, which only has rt_sigreturn. So, references to the old
> non-realtime sigreturn are suspect for new architectures. Similarly,
> references to glibc 2.1.2 are suspect for an architecture with no glibc
> port as of 2.18. (If the Linux ABI isn't fully confirmed with the
> upstream Linux kernel community, you might want to submit the non-Linux
> parts of the GDB port and come back to the Linux parts later.)
Hi Joseph,
This part is based on our outdated glibc 2.5 porting,
and we are still working on glibc 2.18,
so I agree we withdraw this part in revised patch,
and come back when our glibc 2.18 porting is ready.
Thanks for pointing out this and the suggestions.
I will review the patch thoroughly again.
Wei-cheng
next prev parent reply other threads:[~2013-07-09 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 9:28 Wei-cheng Wang
2013-07-08 23:58 ` Joseph S. Myers
2013-07-09 16:18 ` Wei-cheng Wang [this message]
2013-07-09 4:10 ` Yao Qi
2013-07-09 18:23 ` Wei-cheng Wang
2013-07-25 2:35 ` Yao Qi
2013-07-10 5:38 ` Yao Qi
2013-07-11 14:06 ` Wei-cheng Wang
2013-07-11 14:26 ` Wei-cheng Wang
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=51DC37DD.9030709@gmail.com \
--to=cole945@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=joseph@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