From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 48E5F386F012; Wed, 24 Jun 2020 20:45:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 48E5F386F012 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1593031524; bh=sOFcbxuszAJHXd6ryW58phrL7MUTrwDH+kTk+5ragGI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=wzIaw/Bq4cbX7AmZJzy6Kmj7e2Ur6BnTMCd7m2YLERBpFnopLY/4PEqt+baXN+9o2 6u/QOKnG3xwYxMbQ0VE6yNK1mvcTye5eMjQj39Dglj19xMQfe/3ePnwMQgsyRk0u5x 1vC7we+t+mlL4WKe0/ji6hCIrCbSJa8dqwph4nFw= From: "gabravier at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/65832] Inefficient vector construction Date: Wed, 24 Jun 2020 20:45:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: gabravier at gmail dot com X-Bugzilla-Status: NEW 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: cc 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jun 2020 20:45:24 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D65832 Gabriel Ravier changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gabravier at gmail dot com --- Comment #10 from Gabriel Ravier --- Someone might want to look at this, from what I can see it looks like the f= irst few examples are now optimized optimally but I can't say for sure that the later examples are optimized optimally in the same way (it looks like some = of them at least somewhat ideally optimized but some of them are... badly optimized, to say the least).=