From: Oleg Endo <olegendo1024@gmail.com>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [SH] Check FPSCR.PR for fldi0, fldi1 insns in simulator
Date: Tue, 17 Mar 2026 13:50:48 +0900 [thread overview]
Message-ID: <1ca6adbf81c1e1eabeb3360d99a1e92b0f450604.camel@gmail.com> (raw)
In-Reply-To: <33b1b794-d592-45e7-9bb7-53a4a9c45607@simark.ca>
On Mon, 2026-03-16 at 21:19 -0400, Simon Marchi wrote:
>
> On 2026-03-16 21:18, Oleg Endo wrote:
> > On Wed, 2026-03-11 at 10:39 -0400, Simon Marchi wrote:
> > >
> > > Ok, well since we're in "undefined behavior" territory we could argue
> > > that the current sim behavior is fine. But I think the patch is still
> > > good, traping is a more useful behavior to catch something you don't
> > > want to happen.
> >
> > Yes, the current sim behavior is not wrong per se. But like you said,
> > having it trap is more useful for sim's main purpose -- pre-verifying code.
> >
> >
> > > > > The patch LGTM, but I am not a maintainer of the sim, so:
> > > > >
> > > > > Reviewed-By: Simon Marchi <simon.marchi@efficios.com>
> > > > >
> > > > > One note, please put the relevant information (the body of your email)
> > > > > into the commit log itself).
> > > >
> > > > Yeah, sure I can expand the comment of the commit. Updated patch/commit
> > > > attached.
> > >
> > > I would give it a week for Andrew or Mike to review and approve, but
> > > otherwise I would feel comfortable merging it.
> > >
> >
> > Alright. Last time I've checked I had write access. I can commit & push it
> > myself. Just let me know.
>
> Yes, please go ahead.
>
>
Thanks. Committed & pushed as 17eb89e3c1cc6098f08e77d257468486a5c04ce4.
Best regards,
Oleg Endo
prev parent reply other threads:[~2026-03-17 4:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 3:02 Oleg Endo
2026-03-11 4:27 ` Simon Marchi
2026-03-11 6:20 ` Oleg Endo
2026-03-11 14:39 ` Simon Marchi
2026-03-17 1:18 ` Oleg Endo
2026-03-17 1:19 ` Simon Marchi
2026-03-17 4:50 ` Oleg Endo [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=1ca6adbf81c1e1eabeb3360d99a1e92b0f450604.camel@gmail.com \
--to=olegendo1024@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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