From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 12CAB3858D3C; Sun, 6 Feb 2022 13:23:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 12CAB3858D3C From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104117] [9,10,11,12 Regression] Darwin ppc64 uses invalid non-PIC address to access constants (in PIC code). Date: Sun, 06 Feb 2022 13:23:35 +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.3.0 X-Bugzilla-Keywords: link-failure, ra, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: iains 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: 10.4 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: Sun, 06 Feb 2022 13:23:36 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104117 --- Comment #19 from Iain Sandoe --- (In reply to Sergey Fedorov from comment #18) > (In reply to Iain Sandoe from comment #17) > > FTR: this is the patch I came up with: >=20 > Does it affect only ppc64? I am asking since if it affects ppc32, then I > rather rebuild gcc10ppc and gcc11ppc installed on 10.6.8 Rosetta and on > 10A190. While if it matters only for ppc64, then rebuilding on 10.5.8 is > enough. The problem is triggered by deciding to force a constant to memory, in principle that could happen for ppc32 as well [e.g. for a double constant] = (so far, we have not seen an example). Since we build the compiler 'mdynamic-no-pic' for performance, it is not going to show up there [since SYMBOL_REF is a valid address in that case]. Once the patch is tested, posted and applied to master, then we will surely back port to the effected branches.=