From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2141 invoked by alias); 23 Feb 2010 16:32:31 -0000 Received: (qmail 1948 invoked by alias); 23 Feb 2010 16:32:12 -0000 Date: Tue, 23 Feb 2010 16:32:00 -0000 Message-ID: <20100223163212.1947.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c/43128] [4.5 Regression] c-c++-common/pr41779.c doesn't work In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "joseph at codesourcery dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-02/txt/msg02338.txt.bz2 ------- Comment #22 from joseph at codesourcery dot com 2010-02-23 16:32 ------- Subject: Re: [4.5 Regression] c-c++-common/pr41779.c doesn't work On Tue, 23 Feb 2010, manu at gcc dot gnu dot org wrote: > ------- Comment #20 from manu at gcc dot gnu dot org 2010-02-23 08:39 ------- > (In reply to comment #19) > > > > The proposed logic is the same, *except* that the conversion to a common > > type goes via the semantic type, *if* there is excess precision involved > > *and* the operand being converted had integer type. > > In order to know the common_type I need to move the test for build_type before > the calls to convert_and_check. What is build_type for? build_type is for comparisons, when the (semantic) type of the result of the expression is not the same as the (semantic) common type of the operands. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43128