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 6D0E73858C2B; Fri, 21 Apr 2023 17:38:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6D0E73858C2B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1682098732;
	bh=+YzuWLyC9k9K+NSwsRjHMpM8TlTcy6nC0pcUjiAsOzs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=C0Q2xvYLc6p/JMtYI1IAjyawpCdGNN1BSBG9ucvQ7NRDgx83tnI0hX7x0wLqtPHwx
	 Z2Jbiz09CpoatX2ZQEea1+cN0KuLkX4QDoV2uJOZ6akEjVPgMwJeuUiJ8xVygPVbuj
	 OjgtGcFI79ucZe7cclQLaooja7cYxIZFq3NZ1s6U=
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106888] [RISCV] Negative optimization that
 excess andi instructions are generated  in gcc.dg/pr90838.c
Date: Fri, 21 Apr 2023 17:38:51 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106888-4-733zTe2zqk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106888-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106888-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=3D106888

--- Comment #6 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Comment on attachment 54905
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D54905
proposed patch

So that's a subset of what we've done.  We initially thought that was going=
 to
be enough to solve this class of problems.   But it's actually deeper than =
just
having a zero_extension variant of this pattern.=20

I'll officially submit the zero_extension pattern and the match.pd bits.  T=
he
other pattern we wrote is fugly and I'd like to look at it one more time.=