Content deleted Content added
Tomahawkins (talk | contribs) No edit summary |
Tomahawkins (talk | contribs) No edit summary |
||
Line 31:
As a hardware compiler, Atom's primary objective was to maximize the number of operations, or rules, that could execute in a given clock cycle without violating the semantics of atomic operations.
Based on the properties of conflict-free and sequentially-composable rules<ref name="hoe1"/>, Atom's author reduced maximizing execution concurrency to a [[feedback arc set]] optimization of a rule-data dependency graph --
When Atom's author switched careers in late 2007 from logic designer to [[Embedded_systems|embedded software]] engineering, Atom was redesign from an [[hardware description language|HDL]] to a [[___domain specific language]]
targeting [[Realtime_computing|hard realtime]] embedded applications. As a result, Atom's compiler primary objective changed from maximizing rule concurrency to balancing processing load and minimize
[[Worst_case_execution_time|worse case timing latency]].
== Overview ==
|