> There is a recurring theme of people trying to get language/compiler
> support for optimizing particular types: complex, valarray, complex,
> intervals, complex, etc. The problem is that the amount of work is
> large, and the payoff is quite small. If instead we had general
> mechanisms for allowing good optimization of user-defined types, then
> we would no longer have to bug standards committee's with requests for
> special treatment of this type or that type. Instead we could just
> write our libraries, provide some hints to the compiler, and get good
> optimizations for all our types.
I agree. The market is not going support boutique optimization.
(And note that Microsoft decided that F90 itself wasn't worth it!)
For people looking into general mechanisms, I suggest looking at
the PLDI paper on qualifier polymorphism, and, specific to aliasing,
the papers from the late 80's on the FX language. Also learn how
an optimizing compiler really works. The definitive reference these days is:
Muchnick, Steven S., Advanced Compiler Design and Implementation,
Morgan Kaufmann Publishers, Inc., 1997.
Arch D. Robison Kuck & Associates Inc.
robison@kai.com 1906 Fox Drive
217-356-2288 ext. 56 Champaign IL 61820
Lead Developer for KAI C++ http://www.kai.com/C_plus_plus/index.html
--------------------- Object Oriented Numerics List --------------------------
* To subscribe/unsubscribe: use the handy web form at
http://oonumerics.org/oon/
* If this doesn't work, please send a note to owner-oon-list@oonumerics.org
This archive was generated by hypermail 2b29 : Wed Feb 20 2002 - 03:20:11 EST