From: Yao Qi <yao@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch, arm] Skip insns generated by -fstack-protector
Date: Fri, 24 Dec 2010 08:21:00 -0000 [thread overview]
Message-ID: <4D142C48.6000908@codesourcery.com> (raw)
In-Reply-To: <20101223120830.GW2596@adacore.com>
On 12/23/2010 08:08 PM, Joel Brobecker wrote:
>> gdb/
>> * arm-tdep.c (thumb_analyze_prologue): Move some code ...
>> (EXTRACT_MOVW_MOVT_IMM_T): ... here. New macro.
>> (EXTRACT_MOVW_MOVT_IMM_A): New macro.
>> (arm_analyze_load_stack_chk_guard): New.
>> (arm_skip_stack_protector): New.
>> (arm_skip_prologue): Adjust post_prologue_pc by arm_skip_stack_protector.
>
> OK to commit - just watch out that the last line of the ChangeLog
> entry seems a little too long....
>
Committed, with putting "arm_skip_stack_protector." to a new line in
ChangeLog.
http://sourceware.org/ml/gdb-cvs/2010-12/msg00112.html
--
Yao Qi
CodeSourcery
yao@codesourcery.com
(650) 331-3385 x739
prev parent reply other threads:[~2010-12-24 5:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 13:45 Yao Qi
2010-12-20 14:08 ` Yao Qi
2010-12-23 4:16 ` Joel Brobecker
2010-12-23 9:29 ` Yao Qi
2010-12-23 18:29 ` Joel Brobecker
2010-12-24 8:21 ` Yao Qi [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=4D142C48.6000908@codesourcery.com \
--to=yao@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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