Re: Algorithm Optimization

"A. K." <>
Mon, 21 Sep 2020 02:12:37 -0700 (PDT)

          From comp.compilers

Related articles
[6 earlier articles]
Re: Algorithm Optimization (Rick C. Hodgin) (2020-09-16)
Re: Algorithm Optimization (Derek M. Jones) (2020-09-16)
Re: Algorithm Optimization (gah4) (2020-09-16)
Re: Algorithm Optimization (Richard Harnden) (2020-09-16)
Re: Algorithm Optimization (Hans-Peter Diettrich) (2020-09-17)
Re: Algorithm Optimization (Thomas Koenig) (2020-09-17)
Re: Algorithm Optimization (A. K.) (2020-09-21)
| List of all articles for this month |

From: "A. K." <>
Newsgroups: comp.compilers
Date: Mon, 21 Sep 2020 02:12:37 -0700 (PDT)
Organization: Compilers Central
References: 20-09-032 20-09-035 20-09-036 20-09-042
Injection-Info:; posting-host=""; logging-data="17997"; mail-complaints-to=""
Keywords: optimize
Posted-Date: 21 Sep 2020 21:33:06 EDT
In-Reply-To: 20-09-042

Am Sonntag, 20. September 2020 03:06:00 UTC+2 schrieb Hans-Peter Diettrich:
> Am 16.09.2020 um 07:25 schrieb gah4:
> > One thought was that someone codes bubblesort, and the compiler
> > generates quicksort. Small complication that bubblesort is stable, and
> > quicksort isn't. (Add an array with the original position to break ties.)
> Right, algorithm or control flow optimization should be located in an
> earlier project stage, not in compilation. It also smells like the dream
> of automated "proof of correctness", whose basics I learned 50 years ago
> but never found usable results yet. How shall a tool suggest other
> algorithm(s) without knowing (having determined - how?!) about the goals
> of a piece of code?

On a much higher level, (semi)automatic algorithm selection can increase
application productivity enormously.

F.ex. look at the Wolfram language

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.