From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
To: Diego Novillo <dnovillo@redhat.com>
Cc: Joe Buck <Joe.Buck@synopsys.com>, Jeff Law <law@redhat.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: -ffast-math and floating point reordering
Date: Fri, 26 Mar 2004 19:03:00 -0000 [thread overview]
Message-ID: <4064721A.6060905@tat.physik.uni-tuebingen.de> (raw)
In-Reply-To: <1080323297.4600.160.camel@localhost.localdomain>
Diego Novillo wrote:
> On Fri, 2004-03-26 at 12:42, Joe Buck wrote:
>
>
>>One possible representation in GIMPLE would be a flag indicating that a
>>temporary can be, well, I'll call it "refactored" (feel free to suggest a
>>better word). That is, given GIMPLE code like
>>
>> t1 = a + b;
>> t2 = t1 + c;
>> e = t2 + d;
>>
>>if the original Fortran input was
>>
>> e = a + b + c + d
>>
>>then t1 and t2 would be tagged as refactorable, while if the original
>>input were
>>
>> d = ((a + b) + c) + d
>>
>>then t1 and t2 would not be so tagged. In the first case, we would
>>probably want to produce
>>
>> t1 = a + b;
>> t2 = c + d;
>> e = t1 + t2;
>>
>>since the first two additions can now be performed in parallel. But
>>this transformation is not legal in the second case.
>>
>
> Yeah. We sort of discussed adding additional PLUS_EXPR operands and/or
> attributes at last year's summit. But I think that was the extent of
> it. IIRC, there was beer involved, so I doubt anybody was taking notes.
Hmm, this is usually the point where we get the LLVM people tell us what
they are doing here... I consider not being able to do something about
this in tree-ssa a major defect, too.
Richard.
next prev parent reply other threads:[~2004-03-26 18:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 6:03 Joe Buck
2004-03-25 6:05 ` Ian Lance Taylor
2004-03-25 11:27 ` Robert Dewar
2004-03-25 11:31 ` Ian Lance Taylor
2004-03-25 11:55 ` Ben Elliston
2004-03-25 12:37 ` Robert Dewar
2004-03-25 10:22 ` Robert Dewar
2004-03-25 18:28 ` Joe Buck
2004-03-25 18:38 ` Dave Korn
2004-03-26 20:06 ` Robert Dewar
2004-03-26 20:18 ` Joe Buck
2004-03-25 16:12 ` Paul Koning
2004-03-25 18:46 ` Dale Johannesen
2004-03-25 20:11 ` Geert Bosch
2004-03-27 1:51 ` Robert Dewar
2004-03-27 2:39 ` Dale Johannesen
2004-03-26 18:18 ` law
2004-03-26 18:37 ` Joe Buck
2004-03-26 18:46 ` Diego Novillo
2004-03-26 19:03 ` Richard Guenther [this message]
2004-03-26 19:54 ` Fariborz Jahanian
2004-03-26 20:19 ` law
2004-03-26 22:08 ` Joe Buck
2004-03-27 0:42 ` Richard Henderson
2004-03-26 22:12 ` Joseph S. Myers
2004-03-26 21:48 ` Laurent GUERBY
2004-03-26 11:20 Bradley Lucier
2004-03-26 18:33 Robert Dewar
2004-03-26 22:22 Chris Lattner
2004-03-26 22:27 ` Chris Lattner
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=4064721A.6060905@tat.physik.uni-tuebingen.de \
--to=rguenth@tat.physik.uni-tuebingen.de \
--cc=Joe.Buck@synopsys.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=law@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).