CVS difference for ai12s/ai12-0281-1.txt

Differences between 1.5 and version 1.6
Log of other versions for file ai12s/ai12-0281-1.txt

--- ai12s/ai12-0281-1.txt	2019/03/06 05:05:13	1.5
+++ ai12s/ai12-0281-1.txt	2019/03/08 06:57:49	1.6
@@ -338,36 +338,3 @@
 
 ****************************************************************
 
-From: Randy Brukardt
-Sent: Tuesday, February 26, 2018  11:46 PM
-
-When we discussed this AI today, we mentioned that (in general) aspect CPU is 
-not static, so the compiler cannot always know whether or not busy-waiting is 
-needed. We didn't think this is a problem, since aspect CPU is usually static,
-and is always static for profiles Ravenscar/Yorvik.
-
-The Implementation Advice in this AI reads:
-
-   Starting a protected action on a protected object assigned to a processor 
-   should be implemented without busy-waiting.
-
-This is not possible in general, as noted above. Should we fix this wording so 
-it applies only to cases where the implementation could reasonably do the 
-right thing? A strategic insertion of "statically" should do the trick:
-
-   Starting a protected action on a protected object statically assigned to 
-   a processor should be implemented without busy-waiting.
-
-Generally, we try to avoid asking the impossible in implementation advice, and 
-while I suppose it could be accomplished with heroic efforts (generating all 
-of the operations both ways, and picking one at runtime), that would seem to 
-defeat the goal of analysis (especially at the generated code level) and 
-surely efficiency.
-
-That seems especially true in this case, where the advice is as much a 
-statement to users of what they ought to expect as it is to implementers.
-
-Thoughts?
-
-****************************************************************
-

Questions? Ask the ACAA Technical Agent