Path: csiph.com!weretis.net!feeder9.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end
From: John R Levine <johnl@taugh.com>
Newsgroups: comp.compilers
Subject: A paper proposing scheduling languages for compiler optimization
Date: Wed, 30 Oct 2024 15:22:04 -0400
Organization: Compilers Central
Sender: news%iecc.com
Approved: comp.compilers@iecc.com
Message-ID: <24-10-009@comp.compilers>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="26087"; mail-complaints-to="abuse@iecc.com"
Keywords: optimize, preprint
Posted-Date: 30 Oct 2024 15:23:11 EDT
X-submission-address: compilers@iecc.com
X-moderator-address: compilers-request@iecc.com
X-FAQ-and-archives: http://compilers.iecc.com
Xref: csiph.com comp.compilers:3606

Scheduling Languages: A Past, Present, and Future Taxonomy

This paper looks at the way you give a compiler optimization advice,
observes that it's a mess, and proposes defining languages that tell a
compiler how to schedule optimizations. I can't tell whether it's a
clever idea or a reprise of XKCD 927.

https://arxiv.org/abs/2410.19927

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly