Wed, 16 Sep 2020 07:57:05 -0700 (PDT)

Related articles |
---|

Algorithm Optimization rick.c.hodgin@gmail.com (Rick C. Hodgin) (2020-09-13) |

Re: Algorithm Optimization elronnd@elronnd.net (Elijah Stone) (2020-09-14) |

Re: Algorithm Optimization rick.c.hodgin@gmail.com (Rick C. Hodgin) (2020-09-15) |

Re: Algorithm Optimization derek@_NOSPAM_knosof.co.uk (Derek M. Jones) (2020-09-15) |

Re: Algorithm Optimization gah4@u.washington.edu (gah4) (2020-09-15) |

Re: Algorithm Optimization mwmarkland@gmail.com (mwmarkland@gmail.com) (2020-09-16) |

Re: Algorithm Optimization rick.c.hodgin@gmail.com (Rick C. Hodgin) (2020-09-16) |

Re: Algorithm Optimization derek@_NOSPAM_knosof.co.uk (Derek M. Jones) (2020-09-16) |

Re: Algorithm Optimization gah4@u.washington.edu (gah4) (2020-09-16) |

Re: Algorithm Optimization richard.nospam@gmail.com (Richard Harnden) (2020-09-16) |

Re: Algorithm Optimization DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2020-09-17) |

Re: Algorithm Optimization tkoenig@netcologne.de (Thomas Koenig) (2020-09-17) |

[4 later articles] |

From: | "mwmarkland@gmail.com" <mwmarkland@gmail.com> |

Newsgroups: | comp.compilers |

Date: | Wed, 16 Sep 2020 07:57:05 -0700 (PDT) |

Organization: | Compilers Central |

References: | 20-09-032 |

Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="69847"; mail-complaints-to="abuse@iecc.com" |

Keywords: | optimize |

Posted-Date: | 16 Sep 2020 11:14:41 EDT |

In-Reply-To: | 20-09-032 |

On Monday, September 14, 2020 at 9:53:57 PM UTC-5, Rick C. Hodgin wrote:

*> I've been pursuing the idea of what I call algorithm optimization. It's*

*> the idea that algorithms coded by individuals may not be optimal, and*

*> may require refactoring / re-engineering to be made optimal based on*

*> what's trying to be achieved.*

*>*

Example elided for space.

*> Rick C. Hodgin*

*> [I think the usual way to do this is to provide a way to express higher level*

*> algorithms in your programming language so the compiler doesn't have to try*

*> to reverse engineer them. -John]*

I agree that this should usually be the programmer's domain. However

there has been some work done in this area. A book I remember is:

Metzger, Robert. _Automatic Algorithm Recognition and Replacement: A New Approach to Program Optimization_

This approaches the issue more from a "I want to replace serial

algorithms with parallel algorithms." if I recall correctly so it may

not be exactly what you are looking for.

Matt Markland

Post a followup to this message

Return to the
comp.compilers page.

Search the
comp.compilers archives again.