From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A1F2F3951C87; Tue, 28 Apr 2020 17:14:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A1F2F3951C87 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1588094049; bh=2pWR+SSSWJwRoUPZ//dTGWUqVeBUPE9a77Le0czMLqg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Yr3EmqHzI2ILG9BWtgdn3ckPM5Qq4MYfiQd0xkw75LT4QkQs6YgVU0ROYsGImrSfb xZTbetXKIhYZdN8K/I7Xg1kZfVADTw9bK9iZ/NzP0u3MLWjX3gicY+E7nC1/tn2l6M MQ3V1dz3+qkAWXvmF0kGqFAxDsoVltxylx01YOyo= From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/94804] Failure to elide useless movs in 128-bit addition Date: Tue, 28 Apr 2020 17:14:09 +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: 10.0 X-Bugzilla-Keywords: missed-optimization, ra X-Bugzilla-Severity: normal X-Bugzilla-Who: glisse at gcc dot gnu.org 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: 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: Tue, 28 Apr 2020 17:14:09 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94804 --- Comment #4 from Marc Glisse --- (In reply to Gabriel Ravier from comment #3) > Having similar problems with useless movs is from the same non > well-optimized register allocation on function boundaries ? I don't know, but possibly not. I'll shut up because I am not a RA specialist... (and if you expect to see it optimized to bswap64, then obviously it is unrelated to register allocation)=