Ask Slashdot: What's the Most Often-Run Piece of Code -- Ever?

Hugo Villeneuve writes "What piece of code, in a non-assembler format, has been run the most often, ever, on this planet? By 'most often,' I mean the highest number of executions, regardless of CPU type. For the code in question, let's set a lower limit of 3 consecutive lines. For example, is it:

• A UNIX kernel context switch?
• A SHA2 algorithm for Bitcoin mining on an ASIC?
• A scientific calculation running on a supercomputer?
• A 'for-loop' inside on an obscure microcontroller that runs on all GE appliance since the '60s?"

Comments

For / While in C

[Murdoch5]

for(;;){
}

OR

while(1){
}

Starts all main control loops and all kernels.

Re:For / While in C

[Ragzouken]

for(;;)
{
}

while(1)
{
}

Re: For / While in C

[Anonymous Coward]

Perhaps a pixel shader in a modern video game on console or PC, executed per pixel at HD resolution, and for hours (average play time) on tens of millions of machines?

Could be approaching 10^20 executions.

Re:For / While in C

[Dahan]

That actually breaks the C standard, but I suppose control systems aren't much worried about portability.

The ANSI C standard defines two types of implementations: "hosted" and "freestanding". An embedded system would most likely be considered a freestanding implementation, in which case, the entry point function can be whatever the implementation defines it to be. It might not even be named "main" (but if it is, it could return void if that's what the implementation says). That said, C99 allows main() to return void, even in a hosted implementation: 5.1.2.2.1 gives "some other implementation-defined manner." as one of the options for main's definition. It notes in 5.1.2.2.3 that "If the return type is not compatible with int, the termination status returned to the host environment is unspecified."

Re:For / While in C

[FatdogHaiku]

Since no line "maximum" was defined I have to vote for SVCHOST running Windows update on XP....
it keeps going and going and going...

Re: For / While in C

[Zmobie]

I work with a ton of electrical/controls engineers. Yes it is still probably true, mostly because it is still even cheaper/easier to do this through ladder logic. I forget the context of what we were talking about one day, but one day while talking to one of our SENIOR (30+ years) controls engineers I was explaining some logic that if we had to implement it in C# would take probably 300 lines of code. His reply was simply, psh, I could do that in 3 rungs, don't bother.

Re:For / While in C

[jones_supa]

Since no line "maximum" was defined I have to vote for SVCHOST running Windows update on XP....

Just to be accurate... we are shooting the messenger if we blame the SVCHOST process here. It runs various services. The faulty code was in the Windows Update service (wuauserv).

You can see all the respective services with the command tasklist /svc .

Obligatory

[fisted]

Every Ask Slashdot gets a comment pointing out that it's the dumbest Ask Slashdot ever, I know.

This time, it's really, really the case.

Re:Obligatory

[Workaphobia]

I disagree. This may be the superlative of something, but I don't think "dumb" is it.

I actually think it's an interesting thought experiment. It immediately forces the reader to think about how pieces of code are used in the real world, both within and beyond their intended application. But it is also likely impossible to settle to anyone's satisfaction. I would trust a proposed answer to this question even less than I would an answer to "What was the size of the internet at the time of the Morris worm", or "How many lines of C code are there in existence".

Just because something's hard to measure doesn't make it dumb, though.

Re:Obligatory

[d33tah]

Personally I think that the biggest problem with Slashdot is the abundance of comments like this. Seriously, it might not meet your standards. I understand. Now get over it and stop wasting my time writing it for the thousandth time or actually submit an article that raises the bar. Whining is not really going to change anything. Sorry, but I really had to.

Slascode "asciifier"

[psergiu]

Must be the SlashCode "asciifier" which removes all non-ASCII characters in summaries and posts, thus mangling a lot of names, locations and math formulas.

Solved. Next?

[Anonymous Coward]

Question: What piece of code, in a non-assembler format, has been run the most often, ever, on this planet? By 'most often,' I mean the highest number of executions, regardless of CPU type.

Answer: Genetic code.

Re:Bios code?

[Anonymous Coward]

I would probably have to say whatever is the inner loop on the system idle process in windows.

IEFBR14 - Mainframe Null Program

[Anonymous Coward]

http://en.wikipedia.org/wiki/IEFBR14

Any time a mainframe does anything with a dataset in a batch job (i.e. allocate, delete, whatever) it runs IEFBR14, a null program, as a target program to satisfy a requirement in how jobs are created.

This means that banks, retailers, governments, you name it--when they process the back-end records that make modern life functional, IEFBR14 usually gets invoked somewhere.

Re:IEFBR14 - Mainframe Null Program

[sk999]

This gets my vote. Ran it many times myself.

As an aside, this program, (which did absolutely nothing and, in binary format, was originally only 2 bytes long) had the dubious reputation of being the shortest program with a bug. It failed to clear the register that returned the error code. Oops.

Re:Bios code?

[Rockoon]

You are right about the hardware/bios aspect, but arent on the right device.

(nearly) Every computer has a video device which has a loop running over the frame buffer, outputting pixels to the display output port. Even in the days of regular CGA 320x200 graphics on 60hz monitors that amounted to 3,840,000 iterations per second. We are talking over 3 decades of this going on, on nearly every desktop and laptop computer build during that time (vector displays worked differently) and even in those early days of CGA most of the time those machines were in a text mode with a pixel resolution of 720x240 and still putting out a 60hz of video signal (10,368,000 pixels per second.)

A single CGA desktop machine in text mode left on since January 1984 would have output 9,816,000,000,000,000 pixels to its display port so far. Thats nearly 10 quadrillion pixels. Even if the average number of running desktop computers over the period were only 1 million (a severe lowball) and used that shitty low resolution at only 60 hz, thats still over a sextillion iterations of that simple pixel outputting loop.

I would say the average number of running desktops over the period since 1984 is more like 50 million and the average resolution over the period was 1024x768, and the average monitor refresh is 70 hz. My guestimate is about 2.606E+24 iterations of the framebuffer loop, over 2 septillion iterations.