A basic question

consider the following code

Code:

---

#include <stdio.h>

int main(void)
{
    const char *a = "abc";
    const char *b = "abc";
   
    if ( a == b )
        printf("Yes, we are the same!");
       
    getchar();
    return 0;
}

---

Is it guaranteed that the two pointers hold the same address? That's, is the address of the two "abc" the same?

No they don't hold the same address. If you're talking about addresses, try this.

Code:

---

#include <stdio.h>

int main(void)
{
    const char *a = "abc";
    const char *b = "abc";
   
    if ( &a == &b )
        printf("Yes, we are the same!");

    printf("%p \n%p", &a, &b);
       
    getchar();
    return 0;
}

---

No, I didn't mean the addresses of a and b, I meant the address of the two "abc".
I meant the value that a and b hold.

Oh, Try this then.

Code:

---

#include <stdio.h>

int main(void)
{
    const char *a = "abc";  // Reserves memory for 3 characters
    const char *b = "abc";  // Reserves memory for 3 more characters
    const char *x = &a[0];
    const char *y = &b[0];
 
    printf("%p\n%p\n", &x, &y);
       
    getchar();
    return 0;
}

---

Hmm... Let me think this over a bit. I'm all screwed up here.

Quote:

---

From the gcc manual

`-fmerge-constants'
Attempt to merge identical constants (string constants and
floating point constants) across compilation units.

This option is the default for optimized compilation if the
assembler and linker support it. Use `-fno-merge-constants' to
inhibit this behavior.

Enabled at levels `-O', `-O2', `-O3', `-Os'.

---

Because they're the same string, the compiler may choose (or may be told to) merge identical string constants, so writing "abc" twice in the code results in only one "abc" in the executable.
In this case, comparing the pointers will produce a match, but not for the obvious reason (or intent)

So it's up to the compiler to do this, but not guaranteed by the standard. Right?

Your first example was correct. Disregard everything Sly said. You are comparing the two values contained in the pointer, which are addresses. The comparison made in your example would be valid.

Back to the question: The standard doesn't guarintee that two string literals of the same contents be in the same spot in memory. Purely a compiler issue.


Quzah.