[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: DEFINE-OPTIMIZER
- To: sandra%defun@cs.utah.edu
- Subject: Issue: DEFINE-OPTIMIZER
- From: Jim McDonald <jlm@lucid.com>
- Date: Wed, 28 Sep 88 16:40:39 PDT
- Cc: Gray@dsg.csc.ti.com, KMP@stony-brook.scrc.symbolics.com, CL-Compiler@sail.stanford.edu
- In-reply-to: Sandra J Loosemore's message of Wed, 28 Sep 88 17:07:21 MDT <8809282307.AA06910@defun.utah.edu>
One of the nice things about Pitman's proposal is that it is general
enough so that you could use it to implement the kind of rule-based
approach you describe. I tend to agree with Pitman that this is an
advanced feature, and that people who use it will be willing and able
to do that kind of thing.
Does this mean it is fair to assume that if users want to use the
feature across several ports, they will be willing to modify the
(presumably incompatible) optimization routines supplied by different
vendors, and that vendors will be encouraged to release the source
code for their optimizers? (Otherwise optimizers are likely to be
quiet pessimizers, bypassing internal tricks.)
I see nothing inherently wrong with that, but would like it to be clear
that the level of portability may be very low, with parallel
maintenance required for every vendor you port to, and that effective
use will require a moderate amount of documention from the vendors.
jlm