From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5B6103948495; Fri, 20 Mar 2020 17:47:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5B6103948495 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1584726429; bh=50jpvcU5mTyh9tge3eA1o5Yl+KAhwwoYNvVirwuBUdU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=W/1V5NT+erkP8MvXe4hQZTddxqa/AmCVRBJsIv4RIuET5K5M80d0imOJkkPbkxKtJ +kNWsGlmPCr0nilTC03Cp3pVlWIeB3uSaxudjZSbJXpmC27h+j+zFX2KIgeHKfbplX GvXSx1sE01IVUUHUkYXsPqlnvnmro4P4il3PGdGo= From: "ch3root at openwall dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94103] Wrong optimization: reading value of a variable changes its representation for optimizer Date: Fri, 20 Mar 2020 17:47:09 +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: 10.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: ch3root at openwall dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth 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: Fri, 20 Mar 2020 17:47:09 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94103 --- Comment #15 from Alexander Cherepanov --- (In reply to rguenther@suse.de from comment #14) > From a language Pov that's the same. > But memcpy and friends work on any dynamic type so have to copy all bytes. Sorry, I don't understand. Bug 61872, comment 1, and bug 92486, comment 9, = look the same -- a memset followed by an assignment. But the former is with long double while the latter is with a struct. You mean that assignments of structs are equivalent to memcpy while assignm= ents of long doubles aren't? Why the difference?=