From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6F2A63858D32; Mon, 10 Jul 2023 12:37:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6F2A63858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1688992671; bh=4/S5SlF0Ph/5+hpdJHXH24jb0SHAx9EQc+zZsnZrRqg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=HPj4e67lYzxU6QGY2eix+d3RLcLJmmvIwBpfHp2Jf7YTSCjfCFcXKd1rwYOeaXTgY QSe7opjU7F9L7KI+T5HuHgVRQ4M1+Nizmut//9rWhATm3H9WPrYeI1JaX3PDNaaWE3 ShnpXBSRq7bmYe2lOSU0iJ75KIO5AItSZCPQ+UfY= From: "ubizjak at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/110206] [14 Regression] wrong code with -Os -march=cascadelake since r14-1246 Date: Mon, 10 Jul 2023 12:37:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: patch, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: ubizjak at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: ubizjak at gmail dot com X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110206 --- Comment #14 from Uro=C5=A1 Bizjak --- (In reply to Uro=C5=A1 Bizjak from comment #10) > (In reply to Uro=C5=A1 Bizjak from comment #9) > > and simplify_replace_rtx simplifies the above to: > >=20 > > (gdb) p debug_rtx (src) > > (const_vector:V8HI [ > > (const_int 204 [0xcc]) repeated x8 > > ]) >=20 > Patched compiler simplifies to: >=20 > (gdb) p debug_rtx (src) > (const_vector:V8HI [ > (const_int 204 [0xcc]) repeated x4 > (const_int 0 [0]) repeated x4 > ]) The patched compiler puts the above in REG_EQUAL note. While the value is "= more correct", I don't think the compiler has the right to set REG_EQUAL note wh= en the top 4 bytes are actually undefined (as a result of an operation with an undefined input, which is the case with paradoxical subreg).=