Type promotion rules?

[BigMan]

Can someone cite the rules for type promotion in C++?

And, in particular, what is the type of the result of adding 2 values
of type char?

[Bob Hairgrove]

Re: Type promotion rules?

On 12 Jun 2005 12:44:42 -0700, "BigMan" <BigMan@abv.b g> wrote:
[color=blue]
>Can someone cite the rules for type promotion in C++?[/color]

Look for section 4.5 of the standard.
[color=blue]
>And, in particular, what is the type of the result of adding 2 values
>of type char?[/color]

The result of an addition is an rvalue which is implicitly promoted to
type int if necessary, and if an int can contain the resulting value.
This is true on any platform where sizeof(int) > sizeof(char).

But beware of the fact that char might be treated as signed char by
your compiler, though (see my previous reply in a different thread).

--
Bob Hairgrove
NoSpamPlease@Ho me.com

[Me]

Re: Type promotion rules?

> >And, in particular, what is the type of the result of adding 2 values[color=blue][color=green]
> >of type char?[/color]
>
> The result of an addition is an rvalue which is implicitly promoted to
> type int if necessary, and if an int can contain the resulting value.
> This is true on any platform where sizeof(int) > sizeof(char).[/color]

Technically on a platform with sizeof(int) > 1, it can still have a
smaller range than char if the underlying type of char is unsigned char
and the reason int is larger is because of padding bits. But this would
be a very stupid (but allowed) implementation.

[BigMan]

Re: Type promotion rules?

Firstly, according to item 4.5.1 the result of adding 2 chars might be
unsigned int (e.g. when an int cannot represent all the values of a
char). Is this correct?

Secondly, where is it stated that an int can represent all the values
of a signed char if sizeof(int) > sizeof(signed char)?

[BigMan]

Re: Type promotion rules?

What promotions should be performed when compiling this piece of code
if an int can represent all the values of an unsigned short:

unsigned short a = 0;
unsigned int b = 0;
signed int c = 0;
bool d = a < b; // Should a be promoted to int or to unsigned int
according to 4.5.1? Some compilers seem to promote it to unsigned int.
bool e = a < c; // A seems to get promoted to int, which is fine.

[Bob Hairgrove]

Re: Type promotion rules?

On 13 Jun 2005 01:19:33 -0700, "BigMan" <BigMan@abv.b g> wrote:
[color=blue]
>What promotions should be performed when compiling this piece of code
>if an int can represent all the values of an unsigned short:
>
>unsigned short a = 0;
>unsigned int b = 0;
>signed int c = 0;
>bool d = a < b; // Should a be promoted to int or to unsigned int
>according to 4.5.1? Some compilers seem to promote it to unsigned int.[/color]

Neither; bool is an integral type, and "a < b" is a Boolean expression
producing a Boolean result. Both a and b are unsigned integral
expressions. Since the return value is assigned to another Boolean
variable, no conversion or promotion is necessary.

It is possible that some compilers will promote the result of "a<b" to
an rvalue of type unsigned int, then convert that to a Boolean type.
As long as the types involved are all either Boolean or unsigned
integral types, I believe the behavior is well defined by the standard
since Boolean values can only be either 0 or 1 (the Standard says so
somewhere around 4.5 or thereabouts, I'm not sure where, but I saw
it).
[color=blue]
>bool e = a < c; // A seems to get promoted to int, which is fine.[/color]

This is a "horse of an entirely different color". c is signed, a
isn't. Depending on a's value, getting "promoted" to int may cause
problems. It is also possible that c could be promoted to unsigned int
if a were negative when cast to signed. Most compilers would issue a
diagnostic here about "comparing signed with unsigned value" anyway.

--
Bob Hairgrove
NoSpamPlease@Ho me.com

[Old Wolf]

Re: Type promotion rules?

Bob Hairgrove wrote:[color=blue]
>[color=green]
> >What promotions should be performed when compiling this piece of code
> >if an int can represent all the values of an unsigned short:
> >
> >unsigned short a = 0;
> >unsigned int b = 0;
> >signed int c = 0;
> >bool d = a < b; // Should a be promoted to int or to unsigned int
> >according to 4.5.1? Some compilers seem to promote it to unsigned int.[/color]
>
> Neither; bool is an integral type, and "a < b" is a Boolean
> expression producing a Boolean result. Both a and b are unsigned
> integral expressions.
> Since the return value is assigned to another Boolean variable,
> no conversion or promotion is necessary.[/color]

Actually, 'a' is an unsigned short. In this case it will
be promoted to unsigned int, because 'b' is an unsigned int.
[color=blue]
> It is possible that some compilers will promote the result
> of "a<b" to an rvalue of type unsigned int, then convert
> that to a Boolean type.[/color]

If anything, it would be a signed int (promotions only promote
to unsigned int, if the original type doesn't "fit in" a signed
int -- but Bool does).
However I can't think of any way that conforming code could detect
this promotion.
[color=blue]
> As long as the types involved are all either Boolean or unsigned
> integral types, I believe the behavior is well defined by the standard
> since Boolean values can only be either 0 or 1 (the Standard says so
> somewhere around 4.5 or thereabouts, I'm not sure where, but I saw
> it).[/color]

Boolean values can only be true or false. When true is converted
to another integral type, the converted value is 1, etc.
[color=blue][color=green]
> >bool e = a < c; // A seems to get promoted to int,[/color]
>
> This is a "horse of an entirely different color". c is signed, a
> isn't. Depending on a's value, getting "promoted" to int may cause
> problems. It is also possible that c could be promoted to unsigned
> int if a were negative when cast to signed.[/color]

The promotion occurs at compile-time, ie. it doesn't depend
on the value of 'a'. It depends on the possible range of values
of 'a'. If EVERY possible value of 'a' can be represented by a
signed int, the promotion will be to signed int. Otherwise, both
operands will promote to unsigned int.
[color=blue]
> Most compilers would issue a diagnostic here about "comparing signed
> with unsigned value" anyway.[/color]

In my experience, most compilers wouldn't warn for this one,
but would warn for the first example. They apply the default
promotion of 'unsigned short' --> 'signed int' before deciding
whether to issue this warning. Of course, since this diagnostic
is not required, compilers can do what they like.

[BigMan]

Re: Type promotion rules?

> The promotion occurs at compile-time, ie. it doesn't depend[color=blue]
> on the value of 'a'. It depends on the possible range of values
> of 'a'. If EVERY possible value of 'a' can be represented by a
> signed int, the promotion will be to signed int. Otherwise, both
> operands will promote to unsigned int.[/color]

According to item 4.5/1 in the standard integral promotions to signed
int are done without loss of information:

"An rvalue of type char, signed char, unsigned char, short int, or
unsigned short
int can be converted to an rvalue of type int if int can represent all
the values of the source type; otherwise, the source rvalue can be
converted to an rvalue of type unsigned int."

When a signed int cannot represent all the values of the source type,
the promotion is to unsigned int. Does this imply that if a signed int
cannot represent all the values of the source type, then an unsigned
int can?

[Old Wolf]

Re: Type promotion rules?

BigMan wrote:[color=blue][color=green]
> > The promotion occurs at compile-time, ie. it doesn't depend
> > on the value of 'a'. It depends on the possible range of values
> > of 'a'. If EVERY possible value of 'a' can be represented by a
> > signed int, the promotion will be to signed int. Otherwise, both
> > operands will promote to unsigned int.[/color]
>
> According to item 4.5/1 in the standard integral promotions to signed
> int are done without loss of information:
>
> "An rvalue of type char, signed char, unsigned char, short int, or
> unsigned short
> int can be converted to an rvalue of type int if int can represent all
> the values of the source type; otherwise, the source rvalue can be
> converted to an rvalue of type unsigned int."
>
> When a signed int cannot represent all the values of the source type,
> the promotion is to unsigned int. Does this imply that if a signed int
> cannot represent all the values of the source type, then an unsigned
> int can?[/color]

For positive values, it is clear that unsigned int can represent
the value.

For negative values, they can be converted to an unsigned int
by adjusting it modulus (UINT_MAX + 1).

I suppose this conversion is not considered a loss of information
because it is a bijection ("1-1 and onto" correspondence) .

Perhaps asking on comp.std.c or comp.std.c++ would get us a
more accurate answer.