From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-279843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 22527 invoked by alias); 1 Apr 2009 00:36:26 -0000
Received: (qmail 21867 invoked by uid 48); 1 Apr 2009 00:36:09 -0000
Date: Wed, 01 Apr 2009 00:36:00 -0000
Subject: [Bug c/39606]  New: expression statements lose excess precision
X-Bugzilla-Reason: CC
Message-ID: <bug-39606-230@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2009-04/txt/msg00001.txt.bz2

As I noted in <http://gcc.gnu.org/ml/gcc-patches/2008-11/msg00105.html>:
excess precision is removed as part of evaluating an expression statement.
There are two minor problems associated with this:

* If in future GCC preserves such conversions when needed for floating-point
exceptions, the conversions (that are not part of the C99 semantics for
excess precision) will cause spurious exceptions.

* Statement expressions have no excess precision; it would be more natural
for them to have whatever excess precision their last contained expressions
have.


-- 
           Summary: expression statements lose excess precision
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jsm28 at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39606