From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Sandra Loosemore <sandra@codesourcery.com>
Subject: Re: [patch, nios2] Fix bug in nios2 prologue analysis.
Date: Fri, 23 Aug 2019 04:29:00 -0000 [thread overview]
Message-ID: <20190822212902.6f701e62@f29-4.lan> (raw)
In-Reply-To: <bbe0ebc4-9924-1dd5-3976-42f41039a5d7@codesourcery.com>
On Thu, 15 Aug 2019 14:41:43 -0600
Sandra Loosemore <sandra@codesourcery.com> wrote:
> This patch fixes a bug in the nios2 prologue analyzer that was causing
> failures in a couple of test cases. The bug has been there forever, but
> this code isn't terribly well exercised by the testsuite since the nios2
> backend normally uses the dwarf2 unwinder.
>
> I realize the nios2 backend has a more general problem with using int or
> unsigned int to represent target word-sized values when it really ought
> to be using int32_t or uint32_t. I think that is a different issue than
> the signedness bug, though. So, OK to check this in?
Okay.
Kevin
prev parent reply other threads:[~2019-08-23 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 20:41 Sandra Loosemore
2019-08-22 20:12 ` [patch, nios2] [ping] " Sandra Loosemore
2019-08-23 4:29 ` Kevin Buettner [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=20190822212902.6f701e62@f29-4.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sandra@codesourcery.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).