What does this mean: "The compile-time and load-time address-binding methods generate identical logical and physical addresses"? I read this in my Operating System textbook. Does it mean that the logical addresses generated by compile-time binding scheme are the same as the logical addresses generated by load-time binding? Or does it mean that the logical addresses and the physical addresses generated are the same in both compile-time binding as well as load-time binding?

If the first interpretation is correct, then how is it possible to generate same logical addresses in both compile-time and load-time? AFAIK in compile-time binding, we already have a fixed location in the memory where we'll load our program, so we can generate absolute addresses. But in load-time scheme, we do not know where the program will be loaded in memory. So we put relative addresses. How can absolute and relative addresses be the same?
What your TB says is absolutely correct &amp; the answer is the latter i.e. the second interpretation.
More particularly:

The logical address &amp; the physical address generated in the compile-time address binding scheme are the same.
The logical address &amp; the physical address generated in the load-time address binding scheme are the same.

Why?
Context:

Definition of Logical address: A logical address or virtual address is an address that is generated by the CPU during program execution. - afteracademy


Definition of Physical address: physical address refers to a memory address or the location of a memory cell in the main memory - Techopedia

The compile-time binding is used when the base address of the process memory allocation is known before hand i.e. &quot; a priori &quot;. This never happens in real-life because you never know any mechanism/system to predict what the addresses will be at the time of writing the program itself.
However, in case that really happens (How? Static allocation / magic), the address generated by compiler (i.e. the logical address/virtual address) is indeed the actual physical address because the programmer hard-coded the addresses.
Similar (but not same) is the case with Load-time binding.