| Revision as of 04:43, 10 August 2017 editInternetArchiveBot (talk | contribs)Bots, Pending changes reviewers5,381,000 edits Rescuing 1 sources and tagging 0 as dead. #IABot (v1.5beta)← Previous edit | Latest revision as of 17:20, 14 April 2020 edit undoKlbrain (talk | contribs)Autopatrolled, Extended confirmed users, New page reviewers86,503 edits Merged content to Transmeta#Code Morphing Software, redirecting; uncontested 2019 proposal (easy-merge)Tag: New redirect | ||
| (9 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| #REDIRECT ] | |||
| '''Code Morphing Software''' ('''CMS''') is the technology used by ] ] to execute ] instructions.<ref name="cms"> {{webarchive|url=https://web.archive.org/web/20081204122100/http://www.ptlsim.org/papers/transmeta-cgo2003.pdf |date=2008-12-04 }} - Appeared in the Proceedings of the First Annual IEEE/ACM International Symposium on Code Generation and Optimization, 27–29 March 2003, San Francisco, California</ref> In broad view, CMS reads x86 instructions and generates instructions for a proprietary ] processor, in the style of Shade.<ref name="shade"></ref> CMS translation is much more expensive than Shade's, but produces much higher quality code. CMS also contains an interpreter and simulates both user-mode and system mode operation. | |||
| {{R from merge}} | |||
| ==See also== | |||
| {{R to section}} | |||
| *] - similar name, but different purpose | |||
| ==References== | |||
| {{reflist}} | |||
| {{operating-system-stub}} | |||
| ] | ] | ||
| ] | ] | ||
| ] | ] | ||
| ] | |||
Latest revision as of 17:20, 14 April 2020
Redirect to:
- From a merge: This is a redirect from a page that was merged into another page. This redirect was kept in order to preserve the edit history of this page after its content was merged into the content of the target page. Please do not remove the tag that generates this text (unless the need to recreate content on this page has been demonstrated) or delete this page.
- For redirects with substantive page histories that did not result from page merges use {{R with history}} instead.
- To a section: This is a redirect from a topic that does not have its own page to a section of a page on the subject. For redirects to embedded anchors on a page, use {{R to anchor}} instead.