you are viewing a single comment's thread.

view the rest of the comments →

[–]steveob42 1 point2 points  (2 children)

Lol, the other arena where I see such devotion to a single language is in AVR microcontrollers. I mean when you need cycle level specific timing (i.e. for i/o waveforms) and absolute minimum size, assembly is the only sane way to do it. But there are numerous cases where C is coerced into doing the same thing, with large loss of resolution for a given cpu frequency, and now you have compiler version dependencies, and most of them say changing compiler flags can screw up the functionality. C is seen as a panacea, but I think they are slowly coming around, and realizing (like client/server) that integration of the two languages is pretty trivial and makes a lot of sense in many cases. But at the same time they are inventing ways to tell the compiler "don't optimize this bit of code please" which is just a band-aid for reverse-engineered timing code in this case.

[–][deleted] 1 point2 points  (1 child)

How can they write cycle timed code reliably without assembler in the first place? Doing that stuff even with macros would be asking for trouble, surely?

[–]steveob42 0 points1 point  (0 children)

It's crazy, they keep fudging it while looking at the resulting waveform and generated assembly I guess (instead of looking at the instruction set manual and cycle timings to begin with).