SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Intel Corporation (INTC)
INTC 35.53-1.1%Nov 14 3:59 PM EST
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Paul Engel who wrote (78157)4/9/1999 12:44:00 AM
From: Scumbria  Read Replies (3) of 186894
 
Paul,

What are you calling "instruction hazards"?

The whole idea behind VLIW is that data dependencies are managed in software, rather than in hardware. In a traditional microprocessor, the instructions need only be in program order like this:

mov a, b
add a, c
mov b, a

These instructions would execute b = c + b

In a VLIW processor, the instructions not only have to be in order, but they also need to go into the correct "slot" to guarantee correct execution. It may be necessary to add no-ops to this code to make it execute properly on an IA64 CPU.

Obviously the architects are hoping for the user code to be generated only by a select few qualified IA64 compilers, but it is going to be difficult to prevent programmers from engaging in more risky programming practices. It will be interesting to see how it plays out in the real world.

Scumbria
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News