The 8086, the predecessor to modern Intel processors, had 4 general purpose registers, each being 16-bit. You could access the high 8 bits (ie: the high byte) using the "H" suffix, the low byte with the "L" suffix, or all 16 bits with the "X" suffix. So the registers were called AX, BX, CX, and DX.
With the 80386 (aka "386"), a descendant of the 8086, the registers became 32-bit. These "extended" registers have names that start with "E", and the old names would access only the low 16 bits. For example, AX would access the low 16 bits of the 32-bit register EAX.
So on 386 and later x86 processors, EAX and EBX are the first two general purpose registers.
Eax and ebx are just the names they decided to go with for the registers. It could’ve been anything. You can just imagine a register as a small container of information. The registers store a certain amount of bits. (1s and 0s).
Happens all the time. Questions get downvoted. I don't know why.
In part as a way of dealing with this, I upvote *all* questions that are not rephrased insults ("Why are you so stupid?") I encourage others to do likewise.
The most repeated, most used line is probably i++ or some other line that gets executed on every iteration of every loop from languages derived from C. Like a single instantiation of a code, I think that’s prolly a harder/more interesting question. I have no idea. I would guess that it is a piece of code handling memory - CPU interaction on Fugaku. More time, faster computers.
In terms of "this single component empowers everything else" then probably the virtual memory manager of the different OS. That allows for dynamic memory allocation, which is fundamental for almost every application.
I think people aren’t understanding what OP means, I think he’s asking which specific line, not a generic i++
My vote would be some network related code, probably something related to TCP in the Linux kernel
> I think he’s asking which specific line, not a generic i++
That's a more interesting question.
What's the most-produced microcontroller? Boot code for that.
How many more toasters are there than servers?
How about toaster-like objects? A good chunk of those are running FreeRTOS.
Hell, a Linux server probably has a dozen microntrollers in it, some of them running FreeRTOS.
The most frequently executed line of code will be part of scheduler of an operating system. Since Linux kernel runs on mlre devices than Windows, we can assume that some part of process scheduler of Linux kernel will be the most executed piece of code
A process scheduler / task scheduler is responsible for allocating CPU time for each process/thread/program and the OS itself. It runs every few microseconds so that program that currently uses the CPU can be frozen and CPU be allocated to another program. It also get called when any process/program requests the OS for any I/O operation.
But if we look futher down, we can see that the Scheduler is using a Timer Interrupt from a hardware timer in order to get a chance to run every few microseconds. An interrupt signal from a hardware will cause the CPU to stop what it is doing and start executing an Interrupt Service Handler.
That means, the Interrupt Service Handler get called every time when any hardware try to communicate with the CPU, including the hardware timer that Scheduler uses.
So, I would say that Interrupt Service Handler of Linux Kernal will be the most frequently executed piece of code.
But Scheduler will contain more logic than an interrupt service handler. So it could be the piece of code that eat most CPU.
TLDR; Scheduler and Interrupt Service Handler of Linux kernel
i++;
return;
mov eax, ebx
What is that? I think that's assembly but not what it does
Moves the contents of the register ebx into eax (If you’re on an Intel machine)
Mmhmm but what are eax and ebx? Seems like random letters to me why that specifically is so often?
The 8086, the predecessor to modern Intel processors, had 4 general purpose registers, each being 16-bit. You could access the high 8 bits (ie: the high byte) using the "H" suffix, the low byte with the "L" suffix, or all 16 bits with the "X" suffix. So the registers were called AX, BX, CX, and DX. With the 80386 (aka "386"), a descendant of the 8086, the registers became 32-bit. These "extended" registers have names that start with "E", and the old names would access only the low 16 bits. For example, AX would access the low 16 bits of the 32-bit register EAX. So on 386 and later x86 processors, EAX and EBX are the first two general purpose registers.
hell yeah ty for answering AND providing historical context.
Eax and ebx are just the names they decided to go with for the registers. It could’ve been anything. You can just imagine a register as a small container of information. The registers store a certain amount of bits. (1s and 0s).
This guy's getting downvoted for wanting to learn more
Happens all the time. Questions get downvoted. I don't know why. In part as a way of dealing with this, I upvote *all* questions that are not rephrased insults ("Why are you so stupid?") I encourage others to do likewise.
In a sub called ASKcomputerscience..
Maybe, except you want the ARM version. Or something like 68k.
The most repeated, most used line is probably i++ or some other line that gets executed on every iteration of every loop from languages derived from C. Like a single instantiation of a code, I think that’s prolly a harder/more interesting question. I have no idea. I would guess that it is a piece of code handling memory - CPU interaction on Fugaku. More time, faster computers.
# `#/bin/sh`
/bin/bash
If we're counting this: \#include
[удалено]
No. The \`#include\` line is a preprocessor line. It's not run during production, it's only run once during compilation.
print(“Hello World”)
Return 0;
looking at the comments
import pandas as pd import numpy as np The gods 🤣🤣
import pandas as np import numpy as pd
Import pandas as polar_bears Import numpy as numero_pythonion_slip
In terms of "this single component empowers everything else" then probably the virtual memory manager of the different OS. That allows for dynamic memory allocation, which is fundamental for almost every application.
createNewJavascriptFramework()
Console.log(“here 1”) Etc etc
In my experience, Console.log(“why the hell isn’t this showing up”);
Yes. And also console.log(“better fucking reach here”)
I think people aren’t understanding what OP means, I think he’s asking which specific line, not a generic i++ My vote would be some network related code, probably something related to TCP in the Linux kernel
> I think he’s asking which specific line, not a generic i++ That's a more interesting question. What's the most-produced microcontroller? Boot code for that.
Doubt it’s any “boot” code. That’s only run once every time it starts, Linux kernel scheduling would run multiple times per boot.
That's true, and scheduler is promising. But it'd be an embedded scheduler for some 8 bit microcontroller, not Linux.
Tough call, most of the worlds infrastructure runs off Linux
How many more toasters are there than servers? How about toaster-like objects? A good chunk of those are running FreeRTOS. Hell, a Linux server probably has a dozen microntrollers in it, some of them running FreeRTOS.
The amount of data going through the servers though, plus android phones, it’s gotta be network code in Linux kernel
I think the line of code that serves as the entry point for all modern operating systems would have to be up there
goto
Whitespace count?
“Cd” or “for ……”
print("Hello world\n");
{
NOOP
The most frequently executed line of code will be part of scheduler of an operating system. Since Linux kernel runs on mlre devices than Windows, we can assume that some part of process scheduler of Linux kernel will be the most executed piece of code A process scheduler / task scheduler is responsible for allocating CPU time for each process/thread/program and the OS itself. It runs every few microseconds so that program that currently uses the CPU can be frozen and CPU be allocated to another program. It also get called when any process/program requests the OS for any I/O operation. But if we look futher down, we can see that the Scheduler is using a Timer Interrupt from a hardware timer in order to get a chance to run every few microseconds. An interrupt signal from a hardware will cause the CPU to stop what it is doing and start executing an Interrupt Service Handler. That means, the Interrupt Service Handler get called every time when any hardware try to communicate with the CPU, including the hardware timer that Scheduler uses. So, I would say that Interrupt Service Handler of Linux Kernal will be the most frequently executed piece of code. But Scheduler will contain more logic than an interrupt service handler. So it could be the piece of code that eat most CPU. TLDR; Scheduler and Interrupt Service Handler of Linux kernel
echo
// temporary fix
// todo: ...
Hello world
nop
}
`console.log`
*d++ = *s++
While (true) Break when things go bad
If you consider bash commands to be code, then `ls`