Content deleted Content added
Joshfisher (talk | contribs) No edit summary |
No edit summary |
||
Line 1:
I rewrote this article with much more technical content. The previous version was very vague, mentioning making programs parallel. [[User:Dyl|Dyl]] 16:15, Sep 26, 2004 (UTC)
Line 7 ⟶ 9:
Two years ago, someone decided to entitle the grab-bag list of architectural features "Moving Beyond VLIW". This was incorrect, since several of the features were common in VLIWs from the beginning. Saying they were incorporated to improve ILP was correct, however. The actual novel architectural features would be more sensibly included in a list (e.g. the Not-a-Thing bit) called "Moving Beyond VLIW". I'll fix this when I get a chance, though I do think it would make more sense to just incorporate parts of this into the Itanium article, where appropriate. --[[User:Joshfisher|Josh]] ([[User talk:Joshfisher|talk]]) 03:22, 17 November 2008 (UTC)
I am not sure, if this sentence in the article makes sense:
| Each group of multiple software instructions is called a
bundle. Each of the bundles has a stop bit indicating if this
set of operations is depended upon by the subsequent bundle.
This sounds like operations would depend on something, that is executed later.
Shouldn't it be
| Each group of multiple software instructions is called a bundle. Each of the bundles has a stop bit indicating if the
subsequent bundle depend on the result of this set of
operations
or
| Each group of multiple software instructions is called a
bundle. Each of the bundles has a stop bit indicating if this
set of operations depends upon the antecedent bundle.
or
| ... set of operations depends upon the results of the former bundle.
[[Special:Contributions/129.69.50.79|129.69.50.79]] ([[User talk:129.69.50.79|talk]]) 15:10, 15 June 2012 (UTC)
| |||