From: Chris Lattner <sabre@nondot.org>
To: Robert Dewar <dewar@gnat.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: pure and const functions
Date: Mon, 29 Apr 2002 09:34:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0204291124140.26364-100000@nondot.org> (raw)
In-Reply-To: <20020429162319.C2341F29F3@nile.gnat.com>
> I actually think you *do* agree with me. What I said was that it was in
I now agree that I agree with you. :)
I think that:
> 2. Define what the functional effect of declarting something pure is
... is easiest, and should probably be made especially clear in the
documentation, because it is what impacts the user. The problem is that
it has to be updated as new transformations are added...
> 1. Define what pure means semantically
This needs to be well understood by GCC developers that are making the new
transformations... but it would certainly be nice to have. Unfortunately
it's kind of hard to pin down, your sqrt example is a good example of
why. :)
-Chris
http://www.nondot.org/~sabre/os/
http://www.nondot.org/~sabre/Projects/
next prev parent reply other threads:[~2002-04-29 16:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 9:29 Robert Dewar
2002-04-29 9:34 ` Chris Lattner [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-29 17:25 John Wehle
2002-04-29 8:30 Robert Dewar
2002-04-29 8:57 ` Chris Lattner
2002-04-29 8:30 Chris Lattner
2002-04-29 9:23 ` Daniel Berlin
2002-04-29 9:52 ` Chris Lattner
2002-04-29 9:58 ` Mark Dettinger
2002-04-29 5:18 Robert Dewar
2002-04-29 5:44 ` Mark Dettinger
2002-04-29 3:59 Mark Dettinger
2002-04-26 10:17 Chris Lattner
2002-04-26 10:21 ` Kris Warkentin
2002-04-26 10:30 ` Chris Lattner
2002-04-26 10:34 ` Magnus Fromreide
2002-04-26 10:35 ` Chris Lattner
2002-04-26 10:59 ` Magnus Fromreide
2002-04-26 11:03 ` Chris Lattner
2002-04-26 11:27 ` Magnus Fromreide
2002-04-26 12:49 ` Russ Allbery
2002-04-26 10:36 ` Kris Warkentin
2002-04-26 10:46 ` Chris Lattner
2002-04-26 10:26 ` Tim Hollebeek
2002-04-26 10:30 ` Chris Lattner
2002-04-26 10:56 ` Zack Weinberg
2002-04-26 11:01 ` Chris Lattner
2002-08-30 23:02 ` Zack Weinberg
2002-04-26 10:56 ` Tony Finch
2002-04-26 12:11 ` Mark Mitchell
2002-04-26 5:16 Mark Dettinger
2002-04-26 11:20 ` Joseph S. Myers
2002-04-26 12:59 ` Jakub Jelinek
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=Pine.LNX.4.30.0204291124140.26364-100000@nondot.org \
--to=sabre@nondot.org \
--cc=dewar@gnat.com \
--cc=gcc@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).