From: Dave Brolley <brolley@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: [patch][rfa]: Decoding (not-so) ambiguous insns in sid/sim
Date: Thu, 03 Jan 2002 08:20:00 -0000 [thread overview]
Message-ID: <3C3484FA.8070708@redhat.com> (raw)
In-Reply-To: <o58zbgf3x9.fsf@tooth.toronto.redhat.com>
Frank Ch. Eigler wrote:
>brolley wrote:
>
>>[...]
>> (list->vector
>> (map (lambda (p0 p1)
>> (logit 4 p0 "/" p1 " ")
>>! ; (sqrt (+ p0 p1 (* p0 p1))) ; funny function - nice curve
>>! (sqrt (* p0 p1))) ; geometric mean
>> (vector->list 0-population) (vector->list 1-population))))
>>
>
>By the way, have you tried the "funny function" above? It would have
>the property of separating the 0/0 and 0/N cases like your new
>ordering function does, and is monotonic in p0 & p1, so it should not
>change the relative order of existing decoders.
>
Yes, I considered the "funny function" but rejected it because it
assigns a non-zero value in the case where a given bit must always be 1
or always 0, e.g. p0==num_insns,p1==0. Such a bit is useless for
decoding purposes and is correctly assigned a value of zero both by the
old function and by my new function.
Can I consider your response to be approval to commit?
What about "filter-harmlessly-ambiguous-insns"? Should I remove it from
insn.scm?
Dave
next prev parent reply other threads:[~2002-01-03 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C3391D7.6050301.cygnus.project.sid@redhat.com>
2002-01-02 20:34 ` Frank Ch. Eigler
2002-01-03 8:20 ` Dave Brolley [this message]
2002-01-03 8:32 ` Frank Ch. Eigler
2002-01-03 8:47 ` Dave Brolley
2002-01-02 15:03 Dave Brolley
2002-01-03 10:47 ` Dave Brolley
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=3C3484FA.8070708@redhat.com \
--to=brolley@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@redhat.com \
--cc=sid@sources.redhat.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).