From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Aleksandar Markovic <Aleksandar.Markovic@rt-rk.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org, amarkovic@wavecomp.com
Subject: Re: [PULL 3/3] target/mips: Separate FPU-related helpers into their own file
Date: Tue, 4 Feb 2020 09:30:16 +0100 [thread overview]
Message-ID: <88648c41-8825-6063-acb3-9f27f07c011e@redhat.com> (raw)
In-Reply-To: <764d-5e392600-1-7d355c00@99977617>
On 2/4/20 9:06 AM, Aleksandar Markovic wrote:
> > > For clarity and easier maintenence, create
> target/mips/fpu_helper.c, and
> > > move all FPU-related content form target/mips/op_helper.c to that file.
> > >
> > > Signed-off-by: Aleksandar Markovic <amarkovic@wavecomp.com>
> > > Reviewed-by: Aleksandar Rikalo <aleksandar.rikalo@rt-rk.com>
> > > Message-Id:
> <1580745443-24650-3-git-send-email-aleksandar.markovic@rt-rk.com>
> > > ---
> > > target/mips/Makefile.objs | 2 +-
> > > target/mips/fpu_helper.c | 1911
> +++++++++++++++++++++++++++++++++++++++++++++
> > > target/mips/op_helper.c | 1877
> --------------------------------------------
> > > 3 files changed, 1912 insertions(+), 1878 deletions(-)
> > > create mode 100644 target/mips/fpu_helper.c
> > >
> > > diff --git a/target/mips/Makefile.objs b/target/mips/Makefile.objs
> > > index 3ca2bde..91eb691 100644
> > > --- a/target/mips/Makefile.objs
> > > +++ b/target/mips/Makefile.objs
> > > @@ -1,5 +1,5 @@
> > > obj-y += translate.o cpu.o gdbstub.o helper.o
> > > -obj-y += op_helper.o cp0_helper.o
> > > +obj-y += op_helper.o cp0_helper.o fpu_helper.o
> > > obj-y += dsp_helper.o lmi_helper.o msa_helper.o
> > > obj-$(CONFIG_SOFTMMU) += mips-semi.o
> > > obj-$(CONFIG_SOFTMMU) += machine.o cp0_timer.o
> > > diff --git a/target/mips/fpu_helper.c b/target/mips/fpu_helper.c
> > > new file mode 100644
> > > index 0000000..0d5769e
> > > --- /dev/null
> > > +++ b/target/mips/fpu_helper.c
> > > @@ -0,0 +1,1911 @@
> > > +/*
> > > + * Helpers for emulation of CP0-related MIPS instructions.
> >
> > Isn't it "FPU"?
> >
>
> Damn, I did the change, but forgot to do "commit --amend", and that
> passed unnoticed during the rest of procedure.
>
> I just sent PULL v2.
This was not a big deal, we could have updated the comment with another
patch. I was just wondering. Thanks for caring to send a quick v2!
next prev parent reply other threads:[~2020-02-04 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 6:42 [PULL 0/3] MIPS queue for February 4th, 2020 Aleksandar Markovic
2020-02-04 6:42 ` [PULL 1/3] target/mips: Fix ll/sc after 7dd547e5ab6b31e7a0cfc182d3ad131dd55a948f Aleksandar Markovic
2020-02-04 6:42 ` [PULL 2/3] target/mips: Separate CP0-related helpers into their own file Aleksandar Markovic
2020-02-04 6:42 ` [PULL 3/3] target/mips: Separate FPU-related " Aleksandar Markovic
2020-02-04 7:22 ` Philippe Mathieu-Daudé
2020-02-04 8:06 ` Aleksandar Markovic
2020-02-04 8:30 ` Philippe Mathieu-Daudé [this message]
2020-02-04 6:51 ` [PULL 0/3] MIPS queue for February 4th, 2020 no-reply
2020-02-04 8:09 ` Aleksandar Markovic
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=88648c41-8825-6063-acb3-9f27f07c011e@redhat.com \
--to=philmd@redhat.com \
--cc=Aleksandar.Markovic@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).