Sun, 13 Dec 2020 23:13:07 +0100

Related articles |
---|

[7 earlier articles] |

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) |

Re: Algorithm Optimization minforth@arcor.de (A. K.) (2020-09-21) |

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

Re: Algorithm Optimization gah4@u.washington.edu (gah4) (2020-12-20) |

Re: Algorithm Optimization johann@myrkraverk.com (Johann 'Myrkraverk' Oskarsson) (2021-04-21) |

From: | Hans-Peter Diettrich <DrDiettrich1@netscape.net> |

Newsgroups: | comp.compilers |

Date: | Sun, 13 Dec 2020 23:13:07 +0100 |

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="57338"; mail-complaints-to="abuse@iecc.com" |

Keywords: | optimize |

Posted-Date: | 13 Dec 2020 18:16:00 EST |

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

Content-Language: | en-US |

On 13.09.20 19:00, Rick C. Hodgin wrote:

*> 1.*

*>*

*> 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.*

[...]

*> In the above example, a linked list structure is allocated and some data*

*> is stored into it. In this example a single x variable, but in a*

*> real-world case there may be many variables.*

A linked list may be the best solution by itself, but not in some

algorithm. How shall a compiler find out that a linked list here is the

best solution, due to some list features used somewhere else?

*> [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]*

+1

What's the best language to express algorithms in?

Or, how many languages claim that already...

DoDi

Post a followup to this message

Return to the
comp.compilers page.

Search the
comp.compilers archives again.