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 : Advanced Micro Devices - Moderated (AMD)
AMD 213.43+6.2%Dec 19 9:30 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: wanna_bmw who wrote (59376)10/19/2001 6:27:08 PM
From: Gopher BrokeRead Replies (2) of 275872
 
Additionally, changes within a compiler can be tested and implemented in real time. Software only needs to be recompiled to take affect. Hardware changes, on the other hand, require a long design and verification process that can easily last years.

There is the problem in a nutshell. Changing one line of code in the compiler is as risky as a processor core revision and requires as many years of verification.

You produce a new rev of the compiler and it has to work with a lot of legacy code out there. In practice each new rev of a non-EPIC compiler will break your code somewhere, generally in the area of the optimizations it performs. Which is why you tend to freeze the compiler version with the product version.

The more people try and increase the performance of EPIC code by enhancing the compiler optimizations the more they will destabilize the existing codebase. I don't see a happy ending.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext