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 540573858D38; Thu, 11 Apr 2024 11:59:30 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 540573858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712836770;
	bh=xAmH9LblmdcJajsktdRzlQo8lZdvMxtL5b0kCSzAFvI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=UZ2bGhzwnsp6TiVxUEEQTBgu9+NH5OzfTrPKDSNIInnTig3R3PLgd5ngK3DoxiX5w
	 HqSzhpfIcjAnZL3h/wwoEKlM6ekU7EfzxDNpUof3Oz0gfefevwsq8oQB502psjz51I
	 hGDI4t7fdLq54OL9hMKTgk3NERIMuPdGeVg9v0nE=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114693] `expand` introduce redundant store facing logic
 expression
Date: Thu, 11 Apr 2024 11:59:30 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: target_milestone resolution keywords bug_status
Message-ID: <bug-114693-4-vprR4MQ8Li@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114693-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114693-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=3D114693

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |14.0
         Resolution|---                         |FIXED
           Keywords|                            |missed-optimization
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Actually this is fixed on the trunk.

This is what we got in GCC 13 and before:
  g.0_1 =3D g;
  _2 =3D (_Bool) g.0_1;
  _3 =3D (char) _2;
  s.f0 =3D _3;


But in GCC 14+ we get:
  g.0_1 =3D g;
  _2 =3D g.0_1 & 1;
  _3 =3D (char) _2;
  s.f0 =3D _3;


This was fixed by r14-6420-g85c5efcffed19c .=