CVS difference for ai12s/ai12-0125-3.txt

Differences between 1.16 and version 1.17
Log of other versions for file ai12s/ai12-0125-3.txt

--- ai12s/ai12-0125-3.txt	2016/12/28 04:20:39	1.16
+++ ai12s/ai12-0125-3.txt	2017/06/06 01:41:06	1.17
@@ -4127,3 +4127,36 @@
+From: Jeff Cousins
+Sent: Thursday, May 4, 2017  11:14 AM
+[Editor's note: This is in response to the request for HoDs to review AIs
+presented to WG9 for approval. Jeff is presenting UK comments. Only the
+comments on this AI are shown here.]
+I'll be off on holiday for the next fortnight, so here are the only comments
+that I've had so far:
+Would have been so-o-o-o useful in something I've been working on for the last
+couple of decades! - the workarounds are very tedious, and horribly diverse --
+dreadful for legibility when they all represent essentially the same metaphor.
+(And many of the workarounds seem textually identical to cases outside of the
+metaphor, making them bug-prone. So for safety we then have to clutter the
+code with undesirable "clarifier" comments.)
+I'm faintly surprized that the AARM stuff (at least: I'd have put it in the
+question!) doesn't point to the optimization issue when calculating the
+address of @ is slow -- way back in the project I'm in we did the obvious
+"hoisting" optimizations on all repeat addresses, and cut our run-time by
+nearly 30% -- in software for which one "run" is a scatter across many PCs
+then takes months in their otherwise-idle GPU time, that's another turnaround
+per year. That sort of phenomenon must apply in many compute-intensive
+applications, so it merits a bit of prominence.

Questions? Ask the ACAA Technical Agent