This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Unexpected behaviour using unsigned char in comparison

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: "Falk S." <falk-o-mat at gmx dot de>
Cc: gcc-help at gcc dot gnu dot org
Date: Sun, 9 Jan 2011 19:45:44 +0000
Subject: Re: Unexpected behaviour using unsigned char in comparison
References: <4D29F7A4.2070000@gmx.de> <20110109182120.GP23593@axel> <4D2A0B7B.9020806@gmx.de>

On 9 January 2011 19:24, Falk S. wrote:
>
> Ok, that would be the "unexpected". I thought the unary operator~ needs no
> conversion (promotion) and therefore the return type is the same as the
> argument type.

Integral promotions are performed for operator ~ and int can represent
all the values of unsigned char, so the operand is promoted to int.

References:
- Unexpected behaviour using unsigned char in comparison
  - From: Falk S.
- Re: Unexpected behaviour using unsigned char in comparison
  - From: Axel Freyn
- Re: Unexpected behaviour using unsigned char in comparison
  - From: Falk S.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]