From: Tom Tromey <tom@tromey.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: Another fix for the mcore simulator
Date: Tue, 28 Nov 2023 08:09:45 -0700 [thread overview]
Message-ID: <87a5qxewxy.fsf@tromey.com> (raw)
In-Reply-To: <ba69cad8-99db-4779-afa3-12044b6fa2af@gmail.com> (Jeff Law's message of "Mon, 27 Nov 2023 22:46:42 -0700")
>> IIUC gr is a uint32_t so this patch seems like it just removes a
>> zero
>> extension and then a narrowing cast.
Jeff> "gr" is actually a "int32_t", so it's signed.
Aha, say no more. Thank you.
Jeff> Given there's some confusion here, I'll revert it out of my tester
Jeff> which should result in seeing some failures return and I can dive into
Jeff> the simulator again to extract the relevant state in the lsri/lsr
Jeff> instructions.
FWIW I think your patch is fine as-is.
Tom
next prev parent reply other threads:[~2023-11-28 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 18:47 Jeff Law
2023-11-27 20:06 ` Tom Tromey
2023-11-28 5:46 ` Jeff Law
2023-11-28 15:09 ` Tom Tromey [this message]
2023-12-01 2:45 ` Jeff Law
2023-12-01 3:56 ` Tom Tromey
2023-12-01 14:27 ` Jeff Law
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=87a5qxewxy.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=jeffreyalaw@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).