Why is long l = 0x80000000 a positive number?

In C++, why is long l = 0x80000000; positive?

C++:
long l = 0x80000000; // l is positive. Why??

int i = 0x80000000;
long l = i; // l is negative

According to this site: https://en.cppreference.com/w/cpp/language/integer_literal, 0x80000000 should be a signed int but it doesn't appear to be case because when it gets assigned to l sign extension doesn't occur.

Java:
long l = 0x80000000; // l is negative

int i = 0x80000000;
long l = i; // l is negative

On the other hand, Java has a more consistent behavior.

C++ Test code:

#include <stdio.h>
#include <string.h>

void print_sign(long l) {
    if (l < 0) {
        printf("Negative\n");
    } else if (l > 0) {
        printf("Positive\n");
    } else {
        printf("Zero\n");
    }    
}

int main() {
    long l = -0x80000000;
    print_sign(l); // Positive

    long l2 = 0x80000000;
    print_sign(l2); // Positive

    int i =   0x80000000;
    long l3 = i;
    print_sign(l3); // Negative

    int i2 =  -0x80000000;
    long l4 = i2;
    print_sign(l4); // Negative
}

From your link: "The type of the integer literal is the first type in which the value can fit, from the list of types which depends on which numeric base and which integer-suffix was used." and for hexadecimal values lists int, unsigned int...

Your compiler uses 32 bit ints, so the largest (signed) int is 0x7FFFFFFF. The reason a signed int cannot represent 0x8000000...0xFFFFFFF is that it needs some of the 2^32 possible values of its 32 bits to represent negative numbers. However, 0x80000000 fits in an 32 bit unsigned int. You compiler uses 64 bit longs, which can hold up to 0x7FFF FFFF FFFF FFFF, so 0x80000000 also fits in a signed long, and so the long l is the positive value 0x80000000.

On the other hand int i is a signed int and simply doesn't fit 0x80000000, so undefined behaviour occurs. What often happens when a signed number is too big to fit in C++ is that two-complement arithmetic is used and the number wraps round to a large negative number. (Do not rely on this behaviour; optimisations have been known to break this). In any case it appears the two's complement behaviour has indeed happened in this case, resulting in i being negative.

In your example code you use both 0x80000000 and -0x80000000 and in each case they have the same result. In fact, the are the same. Recall that 0x8000000 is an unsigned int. The 2003 C++ standard says in 5.3.1c7: "The negative of an unsigned quantity is computed by subtracting its value from 2^n, where n is the number of bits in the promoted operand." 0x80000000 is precisely 2^31, and so -0x80000000 is 2^32-2^31=2^31. To get the expected behaviours we would have to use -(long)0x80000000 instead.