From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 26A543858D33; Thu, 9 Mar 2023 09:36:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 26A543858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678354576; bh=r2omhj6A7lnjCrvjvTvWZ0SadUZvY1G0Defhp1axE9I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=I2x3A9caRPDeXdHq7clKizCjo/OIx3pmep3S186h2mgySS6mh4lzUXn4iNGx7rtwu sXWm58MXwSR8OmJC34DpC8QJX3E445PjFH5GQwfMh4bZzh4c8f40ji5b56yRbd/Rgv voGnJx8F+UdXd374Q6B5NJ74btP2x1LaH8RC1cGc= From: "tkoenig at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109075] [13 Regression] rnflow hangs at -O3 Date: Thu, 09 Mar 2023 09:36:15 +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: unknown X-Bugzilla-Keywords: needs-bisection X-Bugzilla-Severity: normal X-Bugzilla-Who: tkoenig 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: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_known_to_work 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=3D109075 Thomas Koenig changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |12.2.0 --- Comment #7 from Thomas Koenig --- I've just checked 12.2.0, and the code does not hang there. (In reply to Jakub Jelinek from comment #6) > jmul is used just once, so I wonder if the easiest solution wouldn't be to > make jmul > PARAMETER kind=3D8. We can change the benchmark source, but we cannot change the existing code base using the same idiom out there :-| > Anyway, does -fwrapv work around it too? Yes, -frwapv works. We could just include that in -std=3Dlegacy (it really is used for legacy code) and mention it in the release notes, then. How does that sound?=