From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: dje@watson.ibm.com
Cc: gcc-patches@gcc.gnu.org
Subject: Re: rs6000 fused multiply-add patch [+ patchlet]
Date: Mon, 06 Jan 2003 22:09:00 -0000 [thread overview]
Message-ID: <10301062210.AA12042@vlsi1.ultra.nyu.edu> (raw)
I don't think that anyone is objecting to the concept and the benefit.
If I understand correctly, the patch violates the semantics of the
combiner algorithm which requires a declining cost calculated as the
number of instructions. Allowing combinations that do not decrease
the cost would make the algorithm non-deterministic and possibly not
converge, right?
That's what I'm saying, yes. I'm out of the country right now with poor
email access and will have more to say on this when I et bck in a few days.
next reply other threads:[~2003-01-06 22:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 22:09 Richard Kenner [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-10 2:15 Richard Kenner
2003-01-12 1:38 ` Segher Boessenkool
2003-01-02 1:39 Richard Kenner
2003-01-04 1:59 ` Segher Boessenkool
2002-12-31 3:59 Richard Kenner
2003-01-05 23:24 ` Zack Weinberg
2003-01-06 2:26 ` David Edelsohn
2003-01-06 4:02 ` Segher Boessenkool
2003-01-06 4:07 ` Segher Boessenkool
2003-01-06 23:21 ` Geoff Keating
2003-01-09 22:41 ` Segher Boessenkool
2002-12-30 4:58 Richard Kenner
2002-12-30 20:17 ` Segher Boessenkool
2002-12-30 20:51 ` David Edelsohn
2003-01-02 0:52 ` Segher Boessenkool
2003-01-02 1:44 ` Geoff Keating
2003-01-04 1:59 ` Segher Boessenkool
2002-12-29 5:13 Richard Kenner
2002-12-29 19:25 ` Segher Boessenkool
2002-12-03 17:29 rs6000 fused multiply-add patch David Edelsohn
2002-12-04 19:41 ` Segher Boessenkool
2002-12-05 14:04 ` Geoff Keating
2002-12-20 21:08 ` rs6000 fused multiply-add patch [+ patchlet] Segher Boessenkool
2002-12-20 21:38 ` Geoff Keating
2002-12-20 22:21 ` Segher Boessenkool
2002-12-20 22:28 ` David Edelsohn
2002-12-21 21:55 ` Geoff Keating
2002-12-28 22:08 ` Segher Boessenkool
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=10301062210.AA12042@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=dje@watson.ibm.com \
--cc=gcc-patches@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).