public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.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 10:34:32 +0000 [thread overview] Message-ID: <bug-104117-4-SJY5brzWtk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104117-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104117 --- Comment #15 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Vladimir Makarov from comment #13) > I think there are two code spots whose pitfalls resulted in the PR. > > The first one is in rs6000.cc::legitimate_lo_sum_address_p which permits > wrong pic low-sum address. Ack, > Another one is in lra-constraints.cc::process_address_1 which permits put > wrong low-sum address in reg and use the reg in memory. > > The following patch solves the problem: > > diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c > index 5404fb18755..306f67f26c4 100644 > --- a/gcc/config/rs6000/rs6000.c > +++ b/gcc/config/rs6000/rs6000.c > @@ -8202,7 +8202,7 @@ legitimate_lo_sum_address_p (machine_mode mode, rtx x, > int strict) > { > bool large_toc_ok; > > - if (DEFAULT_ABI == ABI_V4 && flag_pic) > + if ((DEFAULT_ABI == ABI_V4 || DEFAULT_ABI == ABI_DARWIN) && flag_pic) > return false; > /* LRA doesn't use LEGITIMIZE_RELOAD_ADDRESS as it usually calls > push_reload from reload pass code. LEGITIMIZE_RELOAD_ADDRESS I have a somewhat wider fix which accounts for the case that UNSPEC [ SYMBOL_REF ] MACHOPIC_UNSPEC_OFFSET *is* valid, where SYMBOL_REF is not (but the change you have made could be sufficient - will try to get that into a retest soon). > diff --git a/gcc/lra-constraints.c b/gcc/lra-constraints.c > index 30d088afbca..998e82be54f 100644 > --- a/gcc/lra-constraints.c > +++ b/gcc/lra-constraints.c > @@ -3517,21 +3517,8 @@ process_address_1 (int nop, bool check_only_p, > *ad.inner = gen_rtx_LO_SUM (Pmode, new_reg, addr); > if (!valid_address_p (op, &ad, cn)) > { > - /* Try to put lo_sum into register. */ > - insn = emit_insn (gen_rtx_SET > - (new_reg, > - gen_rtx_LO_SUM (Pmode, new_reg, > addr))); > - code = recog_memoized (insn); > - if (code >= 0) > - { > - *ad.inner = new_reg; > - if (!valid_address_p (op, &ad, cn)) > - { > - *ad.inner = addr; > - code = -1; > - } > - } > - > + *ad.inner = addr; > + code = -1; > } > } > if (code < 0) > > The patch was successfully tested on x86-64/ppc64 under Linux. The second part of the patch is the same as what I was testing. How to proceed on this (testing an LRA change widely enough)?
next prev parent reply other threads:[~2022-02-06 10:34 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-19 14:35 [Bug target/104117] New: gcc10 fails to build icu for ppc64 on 10.5.8 (direct access to a floating-point constant) vital.had at gmail dot com 2022-01-19 14:58 ` [Bug target/104117] " iains at gcc dot gnu.org 2022-01-19 15:01 ` iains at gcc dot gnu.org 2022-01-19 15:54 ` vital.had at gmail dot com 2022-01-20 7:36 ` rguenth at gcc dot gnu.org 2022-01-20 7:45 ` iains at gcc dot gnu.org 2022-01-20 8:38 ` iains at gcc dot gnu.org 2022-01-20 14:29 ` [Bug target/104117] [9,10,11,12 Regression] Darwin ppc64 uses invalid non-PIC address to access constants (in PIC code) iains at gcc dot gnu.org 2022-01-20 14:31 ` iains at gcc dot gnu.org 2022-01-20 14:33 ` iains at gcc dot gnu.org 2022-01-20 14:37 ` iains at gcc dot gnu.org 2022-01-20 15:23 ` iains at gcc dot gnu.org 2022-01-22 9:34 ` vital.had at gmail dot com 2022-02-04 22:05 ` vmakarov at gcc dot gnu.org 2022-02-05 8:06 ` vital.had at gmail dot com 2022-02-06 10:34 ` iains at gcc dot gnu.org [this message] 2022-02-06 10:36 ` iains at gcc dot gnu.org 2022-02-06 11:54 ` iains at gcc dot gnu.org 2022-02-06 12:22 ` vital.had at gmail dot com 2022-02-06 13:23 ` iains at gcc dot gnu.org 2022-02-06 15:46 ` iains at gcc dot gnu.org 2022-02-09 15:56 ` vmakarov at gcc dot gnu.org 2022-02-11 2:21 ` vital.had at gmail dot com 2022-02-11 23:52 ` cvs-commit at gcc dot gnu.org 2022-02-13 19:37 ` iains at gcc dot gnu.org 2022-03-04 15:07 ` cvs-commit at gcc dot gnu.org 2022-04-14 5:28 ` cvs-commit at gcc dot gnu.org 2022-05-29 19:12 ` [Bug target/104117] [9,10 " cvs-commit at gcc dot gnu.org 2022-05-29 19:24 ` iains at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-104117-4-SJY5brzWtk@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).