From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>,
Corinna Vinschen <vinschen@redhat.com>
Subject: Re: [PATCH] PR tdep/9390: Fix possible typo on xstorxstormy16-tdep.c
Date: Tue, 16 Sep 2014 20:27:00 -0000 [thread overview]
Message-ID: <54189D34.8010307@redhat.com> (raw)
In-Reply-To: <1410898465-28350-1-git-send-email-sergiodj@redhat.com>
[Adding Corinna, listed as xstormy16 maintainer in MAINTAINERS.
Hi Corinna. Do we still care about this port?]
The fix makes sense to me, though I know nothing about
xstormy16 either.
Thanks,
Pedro Alves
On 09/16/2014 09:14 PM, Sergio Durigan Junior wrote:
> This patch (probably) fixes the bug described in PR tdep/9390, which
> is about a wrong check in the following code:
>
> ...
>
> /* optional copying of args in r2-r7 to r10-r13. */
> /* Probably only in optimized case but legal action for prologue. */
> else if ((inst & 0xff00) == 0x4600 /* 46SD mov rD, rS */
> && (inst & 0x00f0) >= 0x0020 && (inst & 0x00f0) <= 0x0070
> && (inst & 0x000f) >= 0x00a0 && (inst & 0x000f) <= 0x000d)
> ^^^^^^^^^^^^^^^^^^^^^^^^^
> ...
>
> This condition will never trigger, and the fix proposed in the bug
> (which made sense to me) was to test against 0x000a. I tried finding
> documentation about this target, but couldn't find anything. I don't
> even know if it is still used, but decided to submit the fix anyway.
>
> Tested on my x86_64 Fedora 20 GNU/Linux.
>
> gdb/ChangeLog:
> 2014-09-16 Sergio Durigan Junior <sergiodj@redhat.com>
>
> PR tdep/9390
> * xstorxstormy16-tdep.c (xstormy16_analyze_prologue): Fix possible
> typo when using logical AND to determine instruction type.
> ---
> gdb/ChangeLog | 6 ++++++
> gdb/xstormy16-tdep.c | 2 +-
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
> index 8216274..622976d 100644
> --- a/gdb/ChangeLog
> +++ b/gdb/ChangeLog
> @@ -1,5 +1,11 @@
> 2014-09-16 Sergio Durigan Junior <sergiodj@redhat.com>
>
> + PR tdep/9390
> + * xstorxstormy16-tdep.c (xstormy16_analyze_prologue): Fix possible
> + typo when using logical AND to determine instruction type.
> +
> +2014-09-16 Sergio Durigan Junior <sergiodj@redhat.com>
> +
> * objc-lang.c (find_implementation_from_class): Remove dead code.
>
> 2014-09-16 Sergio Durigan Junior <sergiodj@redhat.com>
> diff --git a/gdb/xstormy16-tdep.c b/gdb/xstormy16-tdep.c
> index af3ff32..9692742 100644
> --- a/gdb/xstormy16-tdep.c
> +++ b/gdb/xstormy16-tdep.c
> @@ -374,7 +374,7 @@ xstormy16_analyze_prologue (struct gdbarch *gdbarch,
> /* Probably only in optimized case but legal action for prologue. */
> else if ((inst & 0xff00) == 0x4600 /* 46SD mov rD, rS */
> && (inst & 0x00f0) >= 0x0020 && (inst & 0x00f0) <= 0x0070
> - && (inst & 0x000f) >= 0x00a0 && (inst & 0x000f) <= 0x000d)
> + && (inst & 0x000f) >= 0x000a && (inst & 0x000f) <= 0x000d)
> ;
>
> /* Optional copying of args in r2-r7 to stack. */
>
next prev parent reply other threads:[~2014-09-16 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 20:14 Sergio Durigan Junior
2014-09-16 20:27 ` Pedro Alves [this message]
2014-10-08 8:33 ` Corinna Vinschen
2014-10-09 17:48 ` Sergio Durigan Junior
2014-10-09 18:01 ` Corinna Vinschen
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=54189D34.8010307@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=vinschen@redhat.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