From: Kyle McMartin <kmcmarti@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] aarch64: implement walking over the stack protector
Date: Thu, 05 Jun 2014 20:53:00 -0000 [thread overview]
Message-ID: <20140605205338.GO15355@redacted.bos.redhat.com> (raw)
In-Reply-To: <CA+=Sn1=6wCUvMzUC9MAiGX4+-DL5hEQAm7iRi_=xQ-Rpfo+Dag@mail.gmail.com>
On Thu, Jun 05, 2014 at 01:35:54PM -0700, Andrew Pinski wrote:
> > Finally got a toolchain built that supports ilp32... looks like the
> > existing code should work for it. The only difference (not sure if it's
> > because of gcc HEAD or what) is using w1 instead of x0 repeated for the
> > ldr/str, which looks to be satisfied by the rt/rt2 tests and size=10
> > included in the decode_masked_match. I'll try to build a static ilp32
> > binary to test it meanwhile, but I've had some other issues with gcc
> > HEAD.
>
> Glibc support is not there yet though. I will take over the issue
> with ILP32 then. When this goes in, can you file a bug and assign it
> to me (pinskia@gcc.gnu.org I think is my email for sourceware
> bugzilla)?
>
Will do. Just ran this sequence through the code 'by hand' and it seems
to work on ILP32, fwiw.
--Kyle
prev parent reply other threads:[~2014-06-05 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 5:00 [PATCH 0/2] aarch64: skip over stack protector setup in function prologues Kyle McMartin
2014-06-03 5:02 ` [PATCH 1/2] aarch64: extend decode_adrp to decode immediate offset Kyle McMartin
2014-06-03 8:22 ` Marcus Shawcroft
2014-06-03 14:50 ` Kyle McMartin
2014-06-03 5:03 ` [PATCH 2/2] aarch64: implement walking over the stack protector Kyle McMartin
2014-06-03 5:42 ` Andrew Pinski
2014-06-03 14:51 ` Kyle McMartin
2014-06-05 20:06 ` Kyle McMartin
2014-06-05 20:36 ` Andrew Pinski
2014-06-05 20:53 ` Kyle McMartin [this message]
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=20140605205338.GO15355@redacted.bos.redhat.com \
--to=kmcmarti@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).