From: Yao Qi <qiyaoltc@gmail.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] aarch64 multi-arch support (part 2): siginfo fixup
Date: Fri, 11 Sep 2015 08:39:00 -0000 [thread overview]
Message-ID: <86wpvx5oze.fsf@gmail.com> (raw)
In-Reply-To: <CA+=Sn1nR8s3z+EMKnYvRkeghioCPCDrtjv81yPX5GeSPn4+nWw@mail.gmail.com> (Andrew Pinski's message of "Wed, 9 Sep 2015 00:38:27 +0800")
Andrew Pinski <pinskia@gmail.com> writes:
Hi Andrew,
> This might fix the issue I having with ILP32 and siginfo. Though it
> might be still broken since time_t is 64bit for ILP32 (at least the
> current definition).
You may need separate fixup functions for ILP32, like what we are doing
for x32 on amd64. See amd64-linux-nat.c:amd64_linux_siginfo_fixup.
b.t.w, I find you create a remote branch for gdb-aarch64-ilp32, but I
don't take a look. Out of my curiosity, what is its state now? Is it
ready for submission recently?
--
Yao (齐尧)
next prev parent reply other threads:[~2015-09-11 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 16:30 Yao Qi
2015-09-08 16:38 ` Andrew Pinski
2015-09-11 8:39 ` Yao Qi [this message]
2015-09-11 9:46 ` pinskia
2015-09-15 9:29 ` Yao Qi
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=86wpvx5oze.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=pinskia@gmail.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