From WikiChip
Editing arm/history
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.
Latest revision | Your text | ||
Line 13: | Line 13: | ||
[[Sophie Wilson]] and [[Steve Furber]] designed a reference model in [[BBC BASIC]] in just 808 lines of code. The first processor, the {{armh|ARM1}}, was fabricated on [[VLSI Technology]]'s [[3 µm process]] using just 24,800 transistors. First silicon prototypes were delivered on April 26 1985. | [[Sophie Wilson]] and [[Steve Furber]] designed a reference model in [[BBC BASIC]] in just 808 lines of code. The first processor, the {{armh|ARM1}}, was fabricated on [[VLSI Technology]]'s [[3 µm process]] using just 24,800 transistors. First silicon prototypes were delivered on April 26 1985. | ||
− | The ARM1 had a few major bottlenecks - primarily the lack of hardware [[multiplication]] support resulted in considerable performance issues in related code. The problem was compounded by the fact that the ARM1 had no ability to support [[coprocessors]] which were needed for scientific applications that could make use of a powerful [[FPU]] coprocessor. By the following year Acorn reimplemented the ARM1 on a smaller process along with a number of enhancements designed to address those precise problems | + | The ARM1 had a few major bottlenecks - primarily the lack of hardware [[multiplication]] support resulted in considerable performance issues in related code. The problem was compounded by the fact that the ARM1 had no ability to support [[coprocessors]] which were needed for scientific applications that could make use of a powerful [[FPU]] coprocessor. By the following year Acorn reimplemented the ARM1 on a smaller process along with a number of enhancements designed to address those precise problems. |
== ARM2 & ARM3 == | == ARM2 & ARM3 == |