qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: "Taylor Simpson" <tsimpson@quicinc.com>,
	"Richard Henderson" <rth@twiddle.net>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PULL v2 00/24] target/xtensa updates for 5.2
Date: Tue, 25 Aug 2020 10:33:38 +0100	[thread overview]
Message-ID: <CAFEAcA9SwjPqucXCudSGWpTicfXCS1YXUKGDU9XC1bg7MaP1AA@mail.gmail.com> (raw)
In-Reply-To: <CAMo8BfK+LOyc+HSeBWWyJPEJKGzjJSVqAZ9ZE_XmC3bCfN60fA@mail.gmail.com>

On Mon, 24 Aug 2020 at 22:54, Max Filippov <jcmvbkbc@gmail.com> wrote:
>
> On Mon, Aug 24, 2020 at 2:33 PM Peter Maydell <peter.maydell@linaro.org> wrote:
> > On Sat, 22 Aug 2020 at 20:48, Max Filippov <jcmvbkbc@gmail.com> wrote:
> > > On Sat, Aug 22, 2020 at 3:20 AM Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> > > >
> > > > Where does that come from?
> > >
> > > Generated by xtensa processor generator, as one of many output artifacts.
> >
> > Is there anything different with the source for these cores
> > compared to the ones we already have in the tree, or are
> > these just "more cores, generated the same way as the old ones" ?
>
> They are generated the same way as the old ones, but they have different
> configurations: they support FPU2000 and DFPU opcodes implemented
> earlier in this series. I've added them to enable testing of these opcodes.
> de233_fpu is supposed to be a platform for further xtensa gcc development.

OK, in that case I don't see any reason why we should keep them
out of the tree. Which isn't to shut down the point Philippe has
raised about generated sources, just that there's not much need
to block this pullreq while we have that conversation since it's
not a change from the status-quo.


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/5.2
for any user-visible changes.

-- PMM


  reply	other threads:[~2020-08-25  9:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 20:50 [PULL v2 00/24] target/xtensa updates for 5.2 Max Filippov
2020-08-22 10:20 ` Philippe Mathieu-Daudé
2020-08-22 19:48   ` Max Filippov
2020-08-24 21:33     ` Peter Maydell
2020-08-24 21:54       ` Max Filippov
2020-08-25  9:33         ` Peter Maydell [this message]
2020-08-24  2:43   ` Taylor Simpson

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=CAFEAcA9SwjPqucXCudSGWpTicfXCS1YXUKGDU9XC1bg7MaP1AA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=tsimpson@quicinc.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 NNTP newsgroup(s).