15-513编程语言讲解、辅导Python，c++程序、讲解Java编程设计 解析C/C++编程|讲解R语言编程

日期：2020-10-30 07:12

15-213/18-213/15-513, Summer 2020
Malloc Lab: Writing a Dynamic Storage Allocator
Assigned: Tue, Oct 20
This lab requires submitting two versions of your code: one as an initial checkpoint, and the second
as your final version. The due dates of each part are indicated in the following table:
Version Due Date Max. Grace Days Last Hand-in Date Weight in Final Grade
Checkpoint Oct 29 3 Nov 1 4%
Final Nov 10 3 Nov 13 8%
Don’t forget that due dates are at 11:59pm Eastern Time. See section 7 for details on how each
section is scored.
1 Introduction
In this lab you will write a dynamic memory allocator which will consist of the malloc, free,
realloc, and calloc functions. Your goal is to implement an allocator that is correct, efficient,
and fast.
We strongly encourage you to start early. The total time you spend designing and debugging can
easily eclipse the time you spend coding.
Bugs can be especially pernicious and difficult to track down in an allocator, and you will probably
spend a significant amount of time debugging your code. Buggy code will not get any credit.
This lab has been heavily revised from previous versions. Do not rely on advice or information
you may find on the Web or from people who have done this lab before. It will most likely be
misleading or outright wrong1
. Be sure to read all of the documentation carefully and especially
study the baseline implementation we have provided.
1Not to mention the fact that it would be an academic integrity violation!
1
Contents
1 Introduction 1
2 Logistics 3
3 Required Functions 4
4 Support Routines 6
5 Programming Rules 7
6 Driver Programs 9
6.1 Trace files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.2 Command-line arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7 Scoring 11
7.1 Autograded score . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1.1 Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1.2 Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1.3 Performance index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1.4 Autograded deductions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2 Heap Consistency Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.3 Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.4 Handin Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8 Useful Tips 16
9 Office Hours 17
10 Strategic Advice 18
A Performance Evaluation 20
A.1 Approximate Expected Results from Optimizations . . . . . . . . . . . . . . . . . . . 20
A.2 Machine Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
A.3 Performance Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2
B Viewing Heap Contents with GDB 22
B.1 Viewing the heap without a helper function . . . . . . . . . . . . . . . . . . . . . . . 22
B.2 Viewing the heap with the hprobe helper function . . . . . . . . . . . . . . . . . . . 23
3
2 Logistics
This is an individual project. You should do this lab on one of the Shark machines.
To get your lab materials, click “Download Handout” on Autolab, enter your Andrew ID, and
follow the instructions. Then, clone your repository on a Shark machine by running:
$ git clone https://github.com/cmu15213f20/malloclab-f20-.git
The only file you will turn in is mm.c, which contains your solution. The provided code allows you
to evaluate your implementations. Using the command make will generate four driver programs:
mdriver, mdriver-dbg, mdriver-emulate, and mdriver-uninit, as described in section 6. Your
final autograded score is computed by driver.pl, as described in section 7.1.
To test your code for the checkpoint submission, run mdriver and/or driver.pl with the -C flag.
To test your code for the final submission, you don’t need any additional flags.
You can get some idea of your program performance and the resulting value you will get for the
throughput portion of your grade. However, the Autolab servers will generate different
throughput values, and these will determine your actual score. This is discussed in more
detail in Section 7.
4
3 Required Functions
Your allocator will implement the following functions, declared in mm.h and defined in mm.c:
bool mm_init(void);
void *malloc(size_t size);
void free(void *ptr);
void *realloc(void *ptr, size_t size);
void *calloc(size_t nmemb, size_t size);
bool mm_checkheap(int);
We provide you two versions of memory allocators:
mm.c: A fully-functional implicit-list allocator. We recommend that you use this code as your
starting point.
Note that the provided code does not implement coalesce block(). Although it is a valid
memory allocator, it will result in a high amount of external fragmentation, so you should
implement coalescing. We strongly recommend considering all cases you need to implement
before writing code for this function; the lecture slides should help you identify and reason
about these cases.
mm-naive.c: A functional implementation that runs quickly but gets very poor utilization, because
it never reuses any blocks of memory.
Your allocator must run correctly on a 64-bit machine. It must support a full 64-bit address space,
even though current implementations of x86-64 machines support only a 48-bit address space.
Your submitted mm.c must implement the following functions:
? bool mm_init(void): Performs any necessary initializations, such as allocating the initial
heap area. The return value should be false if there was a problem in performing the
initialization, true otherwise. You must reinitialize all of your data structures in
this function, because the drivers call your mm init function every time they begin a new
trace to reset to an empty heap.
? void *malloc(size_t size): The malloc routine returns a pointer to an allocated block
payload of at least size bytes. The entire allocated block should lie within the heap region
and should not overlap with any other allocated block.
Your malloc implementation must always return 16-byte aligned pointers.
? void free(void *ptr): The free routine frees the block pointed to by ptr. It returns
nothing. This routine is only guaranteed to work when the passed pointer was returned by
an earlier call to malloc, calloc, or realloc and has not yet been freed. free(NULL) has
no effect.
5
? void *realloc(void *ptr, size_t size): The realloc routine returns a pointer to an
allocated region of at least size bytes with the following constraints:
– if ptr is NULL, the call is equivalent to malloc(size);
– if size is equal to zero, the call is equivalent to free(ptr) and should return NULL;
– if ptr is not NULL, the call is equivalent to free(ptr) followed by malloc(size), except
the contents of the new block will be the same as those of the old block, up to the
minimum of the old and new sizes.
Your realloc implementation will have only minimal impact on measured throughput or
utilization. A correct, simple implementation will suffice.
? void *calloc(size_t nmemb, size_t size): Allocates memory for an array of nmemb elements
of size bytes each and returns a pointer to the allocated memory. The memory is set
to zero before returning.
Your calloc will not be graded on throughput or performance. A correct, simple implementation
will suffice.
? bool mm_checkheap(int line): The mm checkheap function (the heap consistency checker,
or simply heap checker) scans the heap and checks it for possible errors.
A quality heap checker is essential for debugging your malloc implementation. Many malloc
bugs are too subtle to debug using conventional gdb techniques. A heap consistency checker
can help you isolate the specific operation that causes your heap to become inconsistent.
Because of the importance of the consistency checker, it will be graded; section 7.2 describes
the requirements for your implementation in greater detail. We may also require you to write
your checkheap function before coming to office hours.
The mm checkheap function takes a single integer argument that you can use any way you
want. One technique is to use this this argument to pass in the line number where it was
called, using the __LINE__ macro:
mm_checkheap(__LINE__);
This allows you to print the line number where mm checkheap was called, if you detect
a problem with the heap. Note, however, that mm checkheap will also be called with an
argument of 0 by the driver.
The semantics for malloc, realloc, calloc, and free match those of the corresponding libc
routines. Type man malloc in the shell for more documentation.
6
4 Support Routines
The memlib.c package simulates the memory system for your dynamic memory allocator. You can
invoke the following functions in memlib.c:
? void *mem sbrk(intptr t incr): Expands the heap by incr bytes, where incr is a nonnegative
integer, and returns a generic pointer to the first byte of the newly allocated heap
area. The semantics are identical to the Unix sbrk function, except that mem sbrk will fail
for negative arguments. (Data type intptr t is defined to be a signed integer large enough
to hold a pointer. On our machines it is 64-bits long.)
? void *mem heap lo(void): Returns a generic pointer to the first valid byte in the heap.
? void *mem heap hi(void): Returns a generic pointer to the last valid byte in the heap.
Careful: the definition of mem heap hi() given here is correct, but it may not be intuitive!
If your heap is 8 bytes large, then the “last valid byte” will be 7 bytes from the start — and
its address will not be aligned.
? size t mem heapsize(void): Returns the current size of the heap in bytes.
You are also allowed to use the following libc library functions: memcpy, memset, printf, fprintf,
and sprintf. Other than these functions and the support routines, your mm.c code may not call
any externally-defined function.
7
5 Programming Rules
? Any allocator that attempts to explicitly detect which trace is running will receive a penalty
of 20 points. On the other hand, you should feel free to write an adaptive allocator—one that
dynamically tunes itself according to the general characteristics of the different traces.
? You should not change any of the interfaces in mm.h, and your program must compile with
the provided Makefile. However, we strongly encourage you to use static helper functions
in mm.c to break up your code into small, easy-to-understand segments.
? You are not allowed to define any large global data structures such as large arrays, trees, or
lists in your mm.c program. However, you are allowed to declare small global arrays, structs
and scalar variables such as integers, floats, and pointers in mm.c. In total, your global
data should sum to at most 128 bytes. Global values defined with the const qualifier
are not counted in the 128 bytes. This will be tested by automated means, as described in
Section 7.1.4.
The reason for this restriction is that the driver cannot account for such global variables in
its memory utilization measure. If you need space for large data structures, you can allocate
space for them within the heap.
? The presence of some undefined behavior is inevitable in malloclab, where we perform unsafe
memory operations and generally treat memory as a giant playground. For example, we
need to do things like cast between pointer types, perform pointer arithmetic, and write to
arbitrary locations in memory. Outside of this lab, it is rarely appropriate to write
code in this style, but it is necessary to do so here.
However, we ask you to minimize the amount of undefined behavior by avoiding it when
possible. For example, instead of directly casting between pointer types, you should explicitly
alias memory through the use of unions. Additionally, you should limit the use of pointer
arithmetic to a few short helper functions, as we have tried to do in the handout code.
? In the provided baseline code, we use a zero-length array to declare a payload element in
the block struct. This is a non-standard compiler extension, but we encourage you to use it
for this lab as a way to explicitly declare your block payload.
One important restriction is that a zero-length array must appear as the last element in its
containing struct. However, for malloclab, we will also permit the use of a zero-length array
as a member of a union, as long as that union is the last element in its containing struct.
This will allow you to explicitly alias the payload with other data that you might also want
to store in the same memory address. Though this is not portable, we strongly encourage its
use compared to the alternative of casting between pointer types.
? The use of macro definitions (using #define) in your code is restricted to the following:
– Macros for debugging purposes, whose names must begin with the prefix “dbg ”.
See, for example, the debugging macros defined in mm.c. You may create your own, but
they must be disabled in submitted code.
8
– Definitions of constants. These definitions must not have any parameters.
The practice of using macros instead of function definitions is now obsolete. Modern compilers
(when optimization is enabled) perform inline substitution of small functions, eliminating any
inefficiencies due to the use of functions rather than macros. In addition, functions provide
better type checking and enable better debugging support.
Here are some examples of allowed and disallowed macro definitions:
#define DEBUG 1 OK Defines a constant
#define CHUNKSIZE (1<<12) OK Defines a constant
#define WSIZE sizeof(uint64 t) OK Defines a constant
#define dbg printf(...) printf( VA ARGS ) OK Debugging support
#define GET(p) (*(unsigned int *)(p)) Not OK Has parameters
#define PACK(size, alloc) ((size)|(alloc)) Not OK Has parameters
When you run make, it will run a program that checks for disallowed macro definitions in your
code. This checker is overly strict—it cannot determine when a macro definition is embedded
in a comment or in some part of the code that has been disabled by conditional-compilation
directives. Nonetheless, your code must pass this checker without any warning messages.
? The code shown in the textbook (Section 9.9.12, and available from the CS:APP website) is
a useful source of inspiration for the lab, but it does not meet the required coding standards.
It does not handle 64-bit allocations, it makes extensive use of macros instead of functions,
and it relies heavily on low-level pointer arithmetic. Similarly, the code shown in K&R does
not satisfy the coding requirements. You should use the provided code mm.c as your starting
point.
? It is okay to look at any high-level descriptions of algorithms found in the textbook or elsewhere,
but it is not acceptable to copy or look at any code of malloc implementations found
online or in other sources, except for the allocators described in the textbook, in K&R, or as
part of the provided code.
? It is okay to adapt code for useful generic data structures and algorithms (e.g., linked lists,
hash tables, search trees, and priority queues) from Wikipedia and other repositories. (This
code must not have already been customized as part of a memory allocator.) You must
include (as a comment) an attribution of the origins of any borrowed code.
? Your allocator must always return pointers that are aligned to 16-byte boundaries. The driver
will check this requirement.
? Your code must compile without warnings.
9
6 Driver Programs
Three driver programs are generated when you run make.
1. mdriver should be used for testing your code’s performance. It checks the correctness, utilization,
and throughput of the standard benchmark traces.
2. mdriver-dbg should be used when debugging your program. This is the same program as
mdriver, with two notable differences:
(a) This program is compiled with DEBUG defined, which enables the dbg_ macros at the
top of mm.c. Without this defined, functions like dbg_printf and dbg_assert will not
have any effect.
(b) Additionally, this program is compiled with optimization level -O0, which allows GDB
to display more meaningful debugging information.
3. mdriver-emulate is used to perform additional correctness checks on your program, which
can result in additional deductions described in section 7.1.4.
It uses special compilation and memory-management techniques to allow testing your program
with a heap making use of the full, 64-bit address space. In addition to the standard
benchmark traces, it will run a set of giant traces with very large allocation requests.
4. mdriver-uninit can be used to detect uses of uninitialized memory, using the MemorySanitizer
tool. It only raises an error when uninitialized memory is actually used, and can track
initialization status down to each bit.
6.1 Trace files
The driver programs are controlled by a set of trace files that are included in the traces subdirectory.
Each trace file contains a sequence of commands that instruct the driver to call your malloc,
realloc, and free routines in some sequence. The drivers and the trace files are the same ones
we will use when we grade your handin mm.c file.
The traces that count towards both your memory utilization and throughput are marked with a
‘*’ in the output of mdriver. Some of the traces are short traces that do not count toward your
memory utilization or throughput but are useful for detecting errors and for debugging, which will
not be marked with a ‘*’ next to them.
When the driver programs are run, they will run each trace file multiple times: once to make sure
your implementation is correct, once to determine the space utilization, and between 3 and 20
times to determine the throughput.
6.2 Command-line arguments
The drivers accept the following command-line arguments. The normal operation is to run it with
no arguments, but you may find it useful to use the arguments during development.
10
? -C: Apply the scoring standards for the checkpoint, rather than for the final submission.
? -f tracefile: Use one particular tracefile instead of the default set of tracefiles for testing
correctness, utilization, and throughput.
? -c tracefile: Run a particular tracefile twice, calling mm init in between each run.
Unlike -t, this option tests only for correctness. This option is extremely useful if you want
to print out debugging messages.
? -v level: Set the verbosity level to the specified value. Levels 0–2 are supported, with a
default level of 1. Raising the verbosity level causes additional diagnostic information to be
printed as each trace file is processed. This can be useful during debugging for determining
which trace file is causing your malloc package to fail.
? -d level: Controls the amount of validity checking performed by the driver. This is entirely
distinct from the DEBUG compile-time define.
At debug level 0, very little checking is done, which is useful when testing performance only.
At debug level 1, the driver checks the payload contents to ensure that they are not overwritten
between calls into your code. This is the default.
At debug level 2, the driver will also call into your implementation of mm checkheap. This
mode is slow, but it can help identify the exact point at which an error occurs.
Additional arguments can be listed by running mdriver -h.
11
7 Scoring
Malloc Lab is worth 11% of your final grade in the course. This is divided into the Checkpoint and
Final submissions, which have separate due dates.
The checkpoint submission, worth 4% of your final grade, is graded as follows:
Autograded score (7.1) 100 points
Heap checker (7.2) 10 points
Total 110 points
The final submission, worth 7% of your final grade, is graded as follows:
Autograded score (7.1) 100 points
Code style (7.3) 12 points
Total 112 points
7.1 Autograded score
driver.pl is the same program that Autolab will use to calculate your score. For the checkpoint
submission, it will be run with the -C flag, which will change the grading standards as described
later in this section.
The program driver.pl computes the autograded score as follows.
? mdriver is run to obtain the performance index P (Section 7.1.3).
? mdriver-emulate is run, which may result in deductions from this score (Section 7.1.4).
Assuming your solution passes all correctness tests, and the graders do not detect any errors in
your source code, two metrics are used to evaluate performance: utilization and throughput.
7.1.1 Utilization
The peak ratio between the aggregate amount of memory used by the driver (i.e., allocated via
malloc but not yet freed via free) and the size of the heap used by your allocator. The optimal
(but unachievable) ratio equals 100%. You should find good policies to minimize fragmentation in
order to make this ratio as high as possible.
The utilization of your allocator U will be calculated as the average utilization across all traces.
The associated score will be computed as follows:
? If U ≤ Umin then you will receive no credit for utilization.
? If Umin < U < Umax then your utilization score will scale linearly with U.
? If U ≥ Umax then you will receive full credit for utilization.
12
Version Umin Umax
Checkpoint 55% 58%
Final 55% 74%
7.1.2 Throughput
Throughput is measured by the average number of operations completed per second, expressed in
kilo-operations per second or KOPS. A trace that takes T seconds to perform n operations will
have a throughput of n/(1000 · T) KOPS.
Throughput measurements vary according to the type of CPU running the program. We will
compensate for this machine dependency by evaluating the throughput of your implementations
relative to those of reference implementations running on the same machine. For information on
how this is done, see Appendix A.2.
The throughput of your allocator T will be calculated as the average throughput across all traces.
This calculation will be based off the reference throughput Tref which will change from checkpoint
to final, and from machine to machine. The associated score will be computed as follows:
? If T ≤ Tmin then you will receive no credit for throughput.
? If Tmin < T < Tmax then your throughput score will scale linearly with T.
? If T ≥ Tmax then you will receive full credit for throughput.
Version Tmin Tmax
Checkpoint 0.1 · Tref 0.8 · Tref
Final 0.5 · Tref 0.9 · Tref
The throughput standards are set low enough that we expect your program will significantly exceed
the requirements for Tmax. Doing so will greatly reduce the frustration of dealing with the different
CPU models and the fluctuations from one run to another caused by the system load.
Note that you will get an indication of your program’s throughput by running it on a Shark machine,
but you must submit it to Autolab to get a reliable calibration.
7.1.3 Performance index
Observing that both memory and CPU cycles are expensive system resources, we combine these
two measures into a single performance index P, with 0 ≤ P ≤ 100, computed as a weighted sum
of the space utilization and throughput:
Version Utilization Throughput
Checkpoint 20% 80%
Final 60% 40%
13
That is, in English, for the checkpoint your score will be computed as 20% utilization and 80%
throughput, and for the final it will be 60% utilization and 40% throughput.
The mdriver driver program will assign a performance index of 0 if it detects an error in any of
the traces.
7.1.4 Autograded deductions
The driver.pl program will also run the mdriver-emulate program (see Section 6), which emulates
a full 64-bit address space. This may deduct points from your autograded score in the
following circumstances:
? If mdriver-emulate fails to run successfully, 30 points will be deducted. This can happen
if your code fails to support a full 64-bit address space; for example, if it uses int where a
size t is needed.
? If the utilization of a trace differs between mdriver and mdriver-emulate, 30 points will
be deducted.
? If your program uses more than 128 bytes of global data (see the Programming Rules in
Section 5), then up to 20 points will be deducted.
7.2 Heap Consistency Checker
10 points will be awarded based on the quality of your implementation of mm checkheap. The heap
checker will be graded for your checkpoint submission only. It will not be graded in your final
submission.
We require that you check all of the invariants of your data structures. Specific items will be
dependent on your design, so after making design changes, think about what changes you need to
make to your heap checker. Some examples of what your heap checker should check:
? Checking the heap (implicit list, explicit list, segregated list):
– Check for epilogue and prologue blocks.
– Check each block’s address alignment.
– Check blocks lie within heap boundaries.
– Check each block’s header and footer: size (minimum size), previous/next allocate/free
bit consistency, header and footer matching each other.
– Check coalescing: no consecutive free blocks in the heap.
? Checking the free list (explicit list, segregated list):
– All next/previous pointers are consistent (if A’s next pointer points to B, B’s previous
pointer should point to A).
14
– All free list pointers are between mem heap lo() and mem heap high().
– Count free blocks by iterating through every block and traversing free list by pointers
and see if they match.
– All blocks in each list bucket fall within bucket size range (segregated list).
Your heap checker should run silently until it detects some error in the heap. Then, and only then,
should it print a message and return false. If it finds no errors, it should return true. It is very
important that your heap checker run silently; otherwise, it will produce too much output to be
useful on the large traces.
7.3 Style
12 points will be awarded based on the quality of your code style, following the Style Guidelines
on the website at http://www.cs.cmu.edu/~213/codeStyle.html. Style will be graded for your
final submission only. It will not be graded for your checkpoint submission.
Some points to keep in mind for malloclab in particular:
? Version control. You must commit your code regularly using Git. This allows you to keep
track of your changes, revert to older versions of your code, and regularly remind yourself of
what you changed and why you made those changes. For specific guidelines on Git usage, see
the style guideline. 2 style points will be awarded based on the frequency of your
commits, and the quality of your messages.
? Modularity. Your code should be decomposed into functions and use as few global variables
as possible. You should use static functions and declared structs and unions to minimize
pointer arithmetic and to isolate it to a few places.
? Magic numbers. You should avoid sprinkling your code with numeric constants. Instead,
use declarations via #define or static constants. Try, as much as possible, to use C data
types, and the operators sizeof and offsetof to define the sizes of various fields and offsets,
rather than using fixed numeric values.
? Header comment. Your mm.c file must begin with a header comment that gives an overview
of the structure of your free and allocated blocks, the organization of the free list, and how
your allocator manipulates the free list.
? Function comments. In addition to the overview header comment, each function must be
preceded by a header comment that describes what the function does. Make sure to review
the course style guide: we are expecting that for each function, you document at a minimum
its purpose, arguments, return value, and any relevant preconditions or postconditions.
? Inline comments. You will want to use inline comments to explain code flow or code that
is tricky.
15
? Extensibility. Your code should be modular, robust, and easily scalable. You should be
able to easily change various parameters that define your allocator, without any changes in
the actual operation of the program. For example, you should be able to arbitrarily change
the number of segregated lists with minimal modifications.
Study the code in mm.c as an example of the desired coding style.
For formatting your code, we require that you use the clang-format tool, which automatically
reformats your code according to the .clang-format configuration file. To invoke it, run make
format. You are welcome to change the configuration settings to match your desired format. More
information is available in the style guideline.
7.4 Handin Instructions
Make sure your code does not print anything during normal operation, and that all debugging
macros have been disabled. Ensure that you have committed and pushed the latest version of your
code to GitHub.
To submit your code, run make submit or upload your mm.c file to Autolab. Only the last version
you submit will be graded.
16
8 Useful Tips
? You’ll find debugging macros defined in mm.c that provide contract functions, such as dbg assert.
We encourage making liberal use of these contracts to verify invariants and ensure correctness
of your code.
? Use the drivers’ -c and -f options to run individual traces. During initial development, using
short trace files will simplify debugging and testing.
? Use the drivers’ verbose mode. The -V option will also indicate when each trace file is
processed, which will help you isolate errors.
? Use gdb to help you debug. This will help you isolate and identify out-of-bounds memory
references. When debugging, use the mdriver-dbg binary, which is compiled with the -O0
flag to disable optimizations.
? Use the Clang static analyzer. The Clang static analyzer is able to find and pinpoint some
bugs and provide explanations for them at compile time. To use it, run make clean and then
run /usr/local/depot/llvm-7.0/bin/scan-build make and look for errors that it found
in your mm.c.
? Use gdb’s watch command to find out what changed some value you did not expect to have
changed.
? Reduce obscure pointer arithmetic through the use of struct’s and union’s. Although your
data structures will be implemented in compressed form within the heap, you should strive to
make them look as conventional as possible using struct and union declarations to encode
the different fields. Examples of this style are shown in the baseline implementation.
? Encapsulate your pointer operations in functions. Pointer arithmetic in memory managers is
confusing and error-prone because of all the casting that is necessary. You can significantly
reduce the complexity by writing functions for your pointer operations. See the code in mm.c
for examples. Remember: you are not allowed to define macros—the code in the textbook
does not meet our coding standards for this lab.
? Your allocator must work for a 64-bit address space. The mdriver-emulate will specifically
test this capability. You should allocate a full eight bytes for all of your pointers and size
fields. (You can take advantage of the low-order bits for some of these values being zero due
to the alignment requirements.) Make sure you do not inadvertently invoke 32-bit arithmetic
with an expression such as 1<<32, rather than 1L<<32.
17
9 Office