News for hackers. Stuff that matters.
Re:Don't remove the $(nop) command below by kibwen on Wednesday February 15, 2017 @05:05PM (#13655789)
Per Moore's law, the number of nops must double every 18 months. For codebases originally written in 1977, the year of make's origin, this now measures in the dozens of meganops.
Re:Don't remove the $(nop) command below by throwanem on Wednesday February 15, 2017 @06:38PM (#13656571)
How apropos! "Dozens of meganops" was my instant reaction to the linked makefile, too.
Re:Don't remove the $(nop) command below by DonHopkins on Wednesday February 15, 2017 @07:55PM (#13657039)
Now you can execute billions of peta-nops in parallel using GPU hardware acceleration in the cloud.
Re:Don't remove the $(nop) command below by Retr0spectrum on Wednesday February 15, 2017 @05:22PM (#13655925)
To be extra pedantic, Moore's law says nothing about clock speed.
Re:Don't remove the $(nop) command below by reitzensteinm on Wednesday February 15, 2017 @06:09PM (#13656353)
To be extra, extra pedantic, clock speed is not the only factor. You must also take in to account the number of NOPs executed per cycle (NPC).

Indeed, chip architects would struggle to find a way to execute vast quantities of NOPs efficiently until the release of the Itanium in 2001.

Re:Don't remove the $(nop) command below by __jal on Wednesday February 15, 2017 @07:55PM (#13657040)
Don't forget the infamous NOP bug that made all the headlines in the late 90s, when certain values of NOP would actually do something.