From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Richard Earnshaw'" <rearnsha@arm.com>
Cc: "'Daniel Jacobowitz'" <dan@codesourcery.com>,
"'Ulrich Weigand'" <uweigand@de.ibm.com>,
<gdb-patches@sourceware.org>
Subject: RE: [RFA] About arm-tdep.c arm_in_function_epilogue_p function
Date: Fri, 19 Nov 2010 08:10:00 -0000 [thread overview]
Message-ID: <003f01cb87c1$352d4bf0$9f87e3d0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <1290088588.7919.1.camel@e102346-lin.cambridge.arm.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Richard Earnshaw
> Envoyé : jeudi 18 novembre 2010 14:56
> À : Pierre Muller
> Cc : 'Daniel Jacobowitz'; 'Ulrich Weigand'; gdb-patches@sourceware.org
> Objet : Re: [RFA] About arm-tdep.c arm_in_function_epilogue_p function
>
>
> On Thu, 2010-11-18 at 14:43 +0100, Pierre Muller wrote:
> > OK, here is the patch.
> >
> > As already said, this patch doesn't change anything on
> > the testsuite results for a armv7l linux machine.
> >
> > > Why don't you just post a patch? Then we can assess it as we would
> all
> > > other patches. The comments in the code at this point clearly
> don't
> > > match the code, so something certainly needs fixing.
> > >
> > > R.
> >
>
> Looking at a wider context I think I see what's happened. The block
> here is essentially a copy of the block earlier in the function with
> s/pc/sp/ applied. Except this one variable wasn't updated properly.
>
> OK.
Thank you for the approval,
patch committed:
http://sourceware.org/ml/gdb-cvs/2010-11/msg00088.html
Pierre
prev parent reply other threads:[~2010-11-19 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 12:19 [RFC] " Pierre Muller
2010-11-16 0:04 ` Daniel Jacobowitz
2010-11-18 11:07 ` Pierre Muller
2010-11-18 13:27 ` Richard Earnshaw
2010-11-18 13:43 ` [RFA] " Pierre Muller
2010-11-18 13:56 ` Richard Earnshaw
2010-11-19 8:10 ` Pierre Muller [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='003f01cb87c1$352d4bf0$9f87e3d0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=rearnsha@arm.com \
--cc=uweigand@de.ibm.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