• R/O
  • SSH

提交

标签
No Tags

Frequently used words (click to add to your profile)

javac++androidlinuxc#windowsobjective-ccocoa誰得qtpythonphprubygameguibathyscaphec計画中(planning stage)翻訳omegatframeworktwitterdomtestvb.netdirectxゲームエンジンbtronarduinopreviewer

Commit MetaInfo

修订版8e890803ce0820b8ed69250b59bb0ca35d5f5e7f (tree)
时间2022-07-08 20:15:17
作者Albert Mietus < albert AT mietus DOT nl >
CommiterAlbert Mietus < albert AT mietus DOT nl >

Log Message

Started with (8) BusyCores-concepts (analyse)

更改概述

差异

diff -r 3edb8e4407e0 -r 8e890803ce08 CCastle/1.Usage/7.BusyCores.rst
--- a/CCastle/1.Usage/7.BusyCores.rst Fri Jul 08 10:45:11 2022 +0200
+++ b/CCastle/1.Usage/7.BusyCores.rst Fri Jul 08 13:15:17 2022 +0200
@@ -216,7 +216,7 @@
216216 enabling --and as Castle supports :ref:`CC` (and is the best language, ever -- so quite close to “ideal”)-- the language
217217 should be designed to enable this.
218218
219-.. use:: In castle is easy to use thousands of cores
219+.. use:: In Castle is easy to use thousands of cores
220220 :ID: U_ManyCore
221221
222222 A “CC Castle” program can run on many cores, without the developer needs to describe “manually” how to do that.
diff -r 3edb8e4407e0 -r 8e890803ce08 CCastle/2.Analyse/8.BusyCores-concepts.rst
--- a/CCastle/2.Analyse/8.BusyCores-concepts.rst Fri Jul 08 10:45:11 2022 +0200
+++ b/CCastle/2.Analyse/8.BusyCores-concepts.rst Fri Jul 08 13:15:17 2022 +0200
@@ -10,17 +10,19 @@
1010 :category: Castle DesignStudy
1111 :tags: Castle, Concurrency
1212
13- In the near future, more and more cores will become available as described in :ref:`BusyCores` And Castle should
14- make it easy to write code for all of them; not to keep them busy, but maximize speed up [useCase:
13+ Shortly, more and more cores will become available alike I described in “:ref:`BusyCores`”. Castle should
14+ make it easy to write code for all of them: not to keep them busy, but to maximize speed up [useCase:
1515 :need:`U_ManyCore`].
1616 |BR|
17- We also discused threads_: they do not scale well for CPU-bound (embedded) systems, and that there are contemporary
18- abstractions on top of them --although they don’t always fit nicely in existing languages.
17+ We also discussed threads_: they do not scale well for CPU-bound (embedded) systems. And I introduced some
18+ contemporary abstractions; which do not always fit nicely in existing languages.
1919
20- As Castle is a new language we have the opportunity to select such a concept, and incorporate it in the language ...
20+ As Castle is a new language we have the opportunity to select such a concept and incorporate it into the language ...
2121
22- In this blog we analyse the options; not focusing in the syntax, but on semantics and implementation details: Does
23- it scale and will it be effectively on many, many cores
22+ In this blog, we explore a bit of theory. I will focus on semantics and the possibilities to implement them
23+ efficiently. The syntactic details come later.
24+
25+
2426
2527
2628 TODO