From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 624283940CE2; Fri, 20 Mar 2020 02:42:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 624283940CE2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1584672155; bh=sLNbn9hQAwl6Cy5wqKUQepEfb0mQHGBUHUVm8qH7E40=; h=From:To:Subject:Date:In-Reply-To:References:From; b=USAty/AyLdN/SfuzeatjfvdySHn/eQf5zPz39navmQQpKCjY2NKV++cTE+hI8q5MW ziIKafGS9nOYVM9y8mYeffPJz2HZR7vvIj74hmklyK9pkA3yRf7Gh9ChT5PeXa1Exz /RBq3LvwsUVHq1aDqX5T0rT84MYSc+oIYoU7Uxe4= From: "pacoarjonilla at yahoo dot es" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/93328] missed optimization opportunity in deserialization code Date: Fri, 20 Mar 2020 02:42:35 +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: 10.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: pacoarjonilla at yahoo dot es 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: Fri, 20 Mar 2020 02:42:35 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D93328 Paco Arjonilla changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pacoarjonilla at yahoo dot= es --- Comment #2 from Paco Arjonilla --- Using shifts and bitwise does not optimize either in GCC master, but it does optimize in CLang. Take this code: #include using type =3D std::uint32_t; type foo(type v){ type r =3D (v << 24) & 0xFF000000; r +=3D (v << 8) & 0x00FF0000; r +=3D (v >> 8) & 0x0000FF00; r +=3D (v >> 24) & 0x000000FF; return r; } CLang assembler output: ( optimize with -O2 ) mov eax, edi bswap eax ret GCC master assembler output: ( optimize with -O2 ) mov eax, edi mov edx, edi shr eax, 24 sal edx, 24 add edx, eax mov eax, edi shr edi, 8 sal eax, 8 and edi, 65280 and eax, 16711680 add eax, edx add eax, edi ret=