From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8C7A53857C42; Fri, 24 Jul 2020 07:10:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8C7A53857C42 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1595574602; bh=FXKw4lk+fNgmclQ+qP0zx/Qwuh7rlA5pwksnnkYF1DE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=sHIgqUbSI3+XRQG9lUfibt5q3MMmGvib8zCwIdm6GxqnHY/K0DFh5FnPcWySljpjP gETKzUojxdIhA3sf/WUKoNs47eOlifga/uvTLSat9zyVYWeQi3RHcyG5D0EIFtX+ks dshTAGLhb3ofBPcAsqR9dF3et/kLgxT4k0qodX14= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96304] Possible mis-compile of SQLite for ARM using gcc 8.3.0 and -O2 Date: Fri, 24 Jul 2020 07:10:02 +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: 8.3.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: Fri, 24 Jul 2020 07:10:02 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96304 --- Comment #4 from Richard Biener --- (In reply to Martin Li=C5=A1ka from comment #3) > > But, are we violating aliasing rules here? What am I missing? >=20 > Likely you are, but I must admit it's sometimes quite difficult to find t= hat. > From quickly looking at the function, you may violate it here: >=20 > MemJournal *p =3D (MemJournal*)pJfd; >=20 > maybe >=20 > MemJournal *p =3D (MemJournal*)(char*)pJfd; >=20 > can solve it. > Unfortunately I can't reproduce it on my x86_64-linux box. An intermediate cast does never solve any strict-aliasing issue.=