From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 103B13858C53; Fri, 21 Jul 2023 06:21:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 103B13858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1689920478; bh=lTDSjW1zvPOhjS87HGBmUFFG46E1lvqF2iI0yxo+AyU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=w3w6/QJaZe8B0QCxIaNOVnMP5o+/cpeN1Mz/4LjrIrM7bos5nkKiZwDl/Cdbk8h6m L/Y7Kk2LCyzEW1xp68eP0F/GshxmkTcTVOu8lITtkzYVq6OFao6navLZ6g7JGTO7Pe FhL06XrN7GQ3u8+YONn8yV1xlMtMfhZn3NPxDAsA= From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/61747] min,max pattern not always properly optimized (for sse4 targets) Date: Fri, 21 Jul 2023 06:21:17 +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: 4.9.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: enhancement X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org 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=3D61747 --- Comment #11 from rguenther at suse dot de --- On Fri, 21 Jul 2023, pinskia at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D61747 >=20 > --- Comment #10 from Andrew Pinski --- > (In reply to CVS Commits from comment #8) > > * g++.target/i386/pr61747.C: New testcase. >=20 > The testcase fails now, I don't know what caused it to fail though: > FAIL: g++.target/i386/pr61747.C -std=3Dgnu++14 scan-assembler-times max= 4 I failed to update it before pushing, it will be fixed with the next push I do (currently re-testing)=