From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 310413861847; Thu, 15 Feb 2024 08:25:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 310413861847 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1707985505; bh=uX10nbo4O2O+ZD3XvScWLokIj80fTxjfYmAfQFA9sFI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=MhY6hUweujqOLjsLHoks68XcbT3v7V3wRvdmlwLzznrUIRKfINRpjlkPt3FBUzwqQ 7MOChoqTcZc9V2E4Iro0eW/s4Tk7RREW5EFOOPW3L6Hg3ml/KDyuroZ1jIqgAFmBp0 UJgLQwzEBxblAHsu/LG4d6V76/6SY4pUJs1IlXhU= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113856] `(vect64 float){1.0f, 0}` code generation could just be `fmov sN, 1.0f` Date: Thu, 15 Feb 2024 08:25:04 +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: 14.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: enhancement X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D113856 --- Comment #3 from Andrew Pinski --- I should note that the one place where `{1.0, 0.0}` shows up is the use with complex :). I found it on accident while understanding why I was getting a failure with `libgomp.c-c++-common/reduction-*.c` where I would also match = on accident `{1.0, 0.0, 1.0, 0.0}`.=