views:

335

answers:

2

Recently I was confused by this question. Maybe because I didn't read language specifications (it's my fault, I know).

C99 standard doesn't say which negative numbers representation should be used by compiler. I always thought that the only right way to store negative numbers is two's complement (in most cases).

So here's my question: do you know any present-day compiler that implements by default one's complement or sign-magnitude representation? Can we change default representation with some compiler flag?

What is the simplest way to determine which representation is used?

And what about C++ standard?

+3  A: 

I think it's not so much a question of what representation the compiler uses, but rather what representation the underlying machine uses. The compiler would be very stupid to pick a representation not supported by the target machine, since that would introduce loads of overhead for no benefit.

Some checksum fields in the IP protocol suite use one's complement, so perhaps dedicated "network accelerator"-type CPU:s implement it.

unwind
Are there any C compilers for "network accelerator"-type CPUs?
klew
@klew: Not that I could find after a few intense minutes of Googling, but that doesn't prove much. :)
unwind
+1  A: 

While twos-complement representation is by far the most common, it is not the only one (see some). The C and C++ standardisation committees did not want to require non-twos-complement machines to emulate a non-native representation. Therefore neither C not C++ require a specific negative integer format.

This leads to the undefined behaviour of bitwise operations on signed types.

Richard
Yes, but it's not what I am asking about. Do you know any C compiler that by default would use non-two's complemet?
klew
Those for systems which use non-tows-complement... Which, apparently, includes some Unisys box which is still supported (this might be listed in the second link).
Richard