Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: THEend8_
CS3214 What to submit: Upload a tar archive that contains a text file answers.txt with your answers for the questions not requiring code, as well as individual files for those that do, as listed below. This exercise is intended to reinforce the content of the lectures related to linking using small examples. As some answers are specific to our current environment, you must again do this exercise on our rlogin cluster. Our verification system will reject your submission if any of the required files are not in your submission. If you want to submit for a partial credit, you still need to include all the above files. 1 CS3214 Fall 2023 Exercise 2 1. Building Software A common task is to use the compiler, linker, and surrounding build systems to build large pieces of software. In this part, you are asked to build a piece of software and observe a typical build process. Your answers will be specific to the version of the GCC tool chain installed on rlogin this semester. 1. Download the source code of Node.js 18.18.0. Read and follow the build instructions in BUILDING.md (note: Omit the ’make install’ step unless you specified a directory to which you have write access as the installation directory (i.e., via the –prefix option to configure). The default installation destination directory is a system directory to which you do not have write access. Hint: lookup the meaning of the -j flag to the make command before running make. Thanks to your engineering fees, make -j64 is ok to use on any rlogin machine. During the make process, identify the link command that produces the node executable and then answer the next two questions. 2. Find the -o flag, which specifies the directory in which the build process will leave the ‘node’ executable post linking. Copy and paste the full path name appearing after -o. 3. Find the location of the static library libuvwasi.a which is given in the link command line. How many .o files does this static library contain? 4. Which libraries are linked dynamically with the node executable (hint: use ldd and ignore linux-vdso.so.1 and /lib64/ld-linux-x86-64.so.2)? 5. List the name of the 4 000th strong global text symbol found in the ‘node’ executable, when considering them in alphabetical order. Hint: use a combination of nm, grep, head, and tail. 6. How much space does the node executable take up on disk? (Use ls -l to find out.) 7. The command size (without any arguments) gives you an estimate of how much memory is needed if the executable were fully loaded into memory. Run size. Roughly what fraction of the executable that is stored on disk would be loaded into memory? 8. The command strip strips an executable of those parts that are not necessary to run it. Run strip on the executable. After stripping the executable, did the stored size of the executable on disk get larger, smaller, or stay the same? 9. After stripping the executable in the previous step, did the amount of memory to run the executable get larger, smaller, or stay the same? 2 CS3214 Fall 2023 Exercise 2 10. Almost half of the text size comes from a single .o module, out/Release/- obj.target/node/gen/node_snapshot.o. Use nm on this file and pipe the output through the c++filt program. Compare the output of this command to the node.js API documentation at https://nodejs.org/dist/latest-v18.x/docs/api/. Research what code and data is contained in this “snapshot” file and how it benefits Node.js. 11. Last, but not least, do not forget to remove the source and build directory from your rlogin file space. It takes up about 1.4GB of space.