From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 398183851C29; Wed,  3 May 2023 15:19:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 398183851C29
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683127165;
	bh=ddOp5crryJP33gZRVx8VrqooOnhwLUmQwjD2n71QFr8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=P0zVC+sWJUU7qXgaukiKEJDIdMFxqNM6/UKG58TKfWf72OFY7f1Kb7MEa4HNRLbJz
	 4DCGHZyC8jMKbqAh74SrNjK0T8wC4fSjyCKDNcad1zbSxtaGOi1BUAmGBg2wfdFQOm
	 5DoKR75FPP/Q+Vwn6fPvg+wh3kSsoKoCViSsE3DQ=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107358] [13 Regression] i686-linux: Since
 r13-3290-g98e341130f8798 code fails to build libjxl-0/7.0 (vector float code)
Date: Wed, 03 May 2023 15:19:24 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107358-4-u4iLxq5A48@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107358-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107358-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107358

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:16bdaf29ff9df3c3c70ecc07bb37511d456d05c6

commit r10-11341-g16bdaf29ff9df3c3c70ecc07bb37511d456d05c6
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Oct 24 17:53:16 2022 +0200

    c, c++: Fix up excess precision handling of scalar_to_vector conversion
[PR107358]

    As mentioned earlier in the C++ excess precision support mail, the
following
    testcase is broken with excess precision both in C and C++ (though just=
 in
C++
    it was triggered in real-world code).
    scalar_to_vector is called in both FEs after the excess precision
promotions
    (or stripping of EXCESS_PRECISION_EXPR), so we can then get invalid
    diagnostics that say float vector + float involves truncation (on ia32
    from long double to float).

    The following patch fixes that by calling scalar_to_vector on the opera=
nds
    before the excess precision promotions, let scalar_to_vector just do the
    diagnostics (it does e.g. fold_for_warn so it will fold
    EXCESS_PRECISION_EXPR around REAL_CST to constants etc.) but will then
    do the actual conversions using the excess precision promoted operands
    (so say if we have vector double + (float + float) we don't actually do
    vector double + (float) ((long double) float + (long double) float)
    but
    vector double + (double) ((long double) float + (long double) float)

    2022-10-24  Jakub Jelinek  <jakub@redhat.com>

            PR c++/107358
    gcc/c/
            * c-typeck.c (build_binary_op): Pass operands before excess
precision
            promotions to scalar_to_vector call.
    gcc/testsuite/
            * c-c++-common/pr107358.c: New test.

    (cherry picked from commit 65e3274e363cb2c6bfe6b5e648916eb7696f7e2f)=