qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Jia Liu <proljc@gmail.com>
Cc: sw@weilnetz.de, qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH V2 0/4] MIPS ASE DSP Support for Qemu
Date: Fri, 23 Mar 2012 09:01:36 -0700	[thread overview]
Message-ID: <4F6C9E60.9040803@twiddle.net> (raw)
In-Reply-To: <1332423372-2391-1-git-send-email-proljc@gmail.com>

> +DEF_HELPER_1(absqsph, i32, i32)

Many of these helpers merely compute a function.  They do not trap,
they do not modify global state.  They should be using the 
DEF_HELPER_FLAGS_N macro to define them, so that the TCG compiler
can optimize around the functions better.

>  target-mips/op_helper.c | 3936 +++++++++++++++++++++++++++++++++++++++++++++++
>  1 files changed, 3936 insertions(+), 0 deletions(-)

Nearly 4000 lines to me says: put these in their own file.

It would be my preference if this were done in a way that
exposes any implicit uses of the ENV variable.  But even
failing that, the makefile can be adjusted to apply HELPER_CFLAGS
to other helper files.


r~

  parent reply	other threads:[~2012-03-23 16:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 13:36 [Qemu-devel] [PATCH V2 0/4] MIPS ASE DSP Support for Qemu Jia Liu
2012-03-22 13:36 ` [Qemu-devel] [PATCH V2 1/4] add MIPS DSP helpers define Jia Liu
2012-03-22 13:36 ` [Qemu-devel] [PATCH V2 2/4] add MIPS DSP helpers implement Jia Liu
2012-03-22 13:54   ` Peter Maydell
2012-03-23  1:24     ` Jia Liu
2012-03-22 13:36 ` [Qemu-devel] [PATCH V2 3/4] add MIPS DSP translation Jia Liu
2012-03-22 13:36 ` [Qemu-devel] [PATCH V2 4/4] add MIPS DSP testcase Jia Liu
2012-03-22 14:01 ` [Qemu-devel] [PATCH V2 0/4] MIPS ASE DSP Support for Qemu Peter Maydell
2012-03-23  1:40   ` Jia Liu
2012-03-23  7:21   ` 陳韋任
2012-03-22 14:03 ` Peter Maydell
2012-03-23  1:31   ` Jia Liu
2012-03-23 16:01 ` Richard Henderson [this message]
2012-03-26  1:07   ` Jia Liu

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=4F6C9E60.9040803@twiddle.net \
    --to=rth@twiddle.net \
    --cc=aurelien@aurel32.net \
    --cc=proljc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).