memory-user.c

[Nwb4iNh0]

Can someone write comments on this code to be more understandable

  

#include <stdio.h>
#include <stdlib.h>
#define NITER 10000
int main(int argc, char *argv[]) {
if (argc != 2) {
fprintf(stderr, "usage: memory-user <memory>\n");
exit(EXIT_FAILURE);
}
int memory = atoi(argv[1]) * 1024 * 1024;
int length = (int)(memory / sizeof(int));
int *arr = malloc(memory);
if (arr == NULL) {
fprintf(stderr, "malloc failed\n");
}
for (int i = 0; i < NITER; i++) {
for (int j = 0; j < length; j++) arr[j] += 1;
}
}
free(arr);
return 0;

[Ganado]

The code appears to just be copied from somewhere, so as far as we can tell, you have shown zero effort in tackling this assignment.

Tell us specifically where you start to not understand the code, and we can help you bit by bit instead of just writing the comments for you. Give us a guess at what you think a line you don't understand is doing. If it's a certain keyword or function you don't understand, try searching it online.

Seems to be modified from https://github.com/xxyzz/ostep-hw/blob/master/13/memory-user.c

[jonnin]

that code does not do anything.
I mean it pokes values into the piratey arr variable and then throws the values away, zero sum game of nothing accomplished. It looks like a quick example of how to use malloc, at a guess? Its a little hard to read with the braces not aligned and the bad variable names and such.

[deleted account xyzzy]

"Properly" formatted reveals this code snippet is a huge steaming pile of manure that shouldn't compile:

#include <stdio.h>
#include <stdlib.h>
#define NITER 10000
int main(int argc, char* argv[])
{
   if (argc != 2)
   {
      fprintf(stderr, "usage: memory-user <memory>\n");
      exit(EXIT_FAILURE);
   }
   int memory = atoi(argv[1]) * 1024 * 1024;
   int length = (int)(memory / sizeof(int));
   int* arr = malloc(memory);
   if (arr == NULL)
   {
      fprintf(stderr, "malloc failed\n");
   }
   for (int i = 0; i < NITER; i++)
   {
      for (int j = 0; j < length; j++) arr[j] += 1;
   }
}
free(arr);
return 0;

[JLBorges]

It can do something that surprises us; the program may engender undefined behaviour.

malloc allocates uninitialized storage; the program tries to increment uninitialized scalars.

(atoi may cause undefined behaviour if the converted integer value is outside of range,
strtol is a safer alternative)