public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94145] Longcalls mis-optimize loading the function address Date: Fri, 01 May 2020 01:18:16 +0000 [thread overview] Message-ID: <bug-94145-4-FozUcuTJbU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94145-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94145 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Alan Modra <amodra@gcc.gnu.org>: https://gcc.gnu.org/g:0c3519218fb11bdde5356aec9fcac133b4988698 commit r9-8556-g0c3519218fb11bdde5356aec9fcac133b4988698 Author: Alan Modra <amodra@gmail.com> Date: Wed Mar 11 21:22:37 2020 +1030 [RS6000] PR94145, make PLT loads volatile PR target/94145 * config/rs6000/rs6000.c (rs6000_longcall_ref): Use unspec_volatile for PLT16_LO. * config/rs6000/rs6000.md (UNSPEC_PLT16_LO): Remove. (UNSPECV_PLT16_LO): Define. (pltseq_plt16_lo_): Use unspec_volatile. (cherry picked from commit 19e5389debb03c3623f6a2ce8a8f6f4aa2118901) minus the PLT_PCREL parts
next prev parent reply other threads:[~2020-05-01 1:18 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-11 16:00 [Bug target/94145] New: " meissner at gcc dot gnu.org 2020-03-11 18:27 ` [Bug target/94145] " meissner at gcc dot gnu.org 2020-03-11 21:33 ` segher at gcc dot gnu.org 2020-03-11 21:35 ` segher at gcc dot gnu.org 2020-03-11 22:50 ` amodra at gmail dot com 2020-03-11 22:50 ` amodra at gmail dot com 2020-03-12 8:48 ` rguenth at gcc dot gnu.org 2020-03-12 13:00 ` amodra at gmail dot com 2020-03-12 13:17 ` rguenth at gcc dot gnu.org 2020-03-12 13:34 ` amodra at gmail dot com 2020-03-12 13:57 ` rguenth at gcc dot gnu.org 2020-03-12 15:38 ` segher at gcc dot gnu.org 2020-03-27 22:16 ` cvs-commit at gcc dot gnu.org 2020-05-01 1:18 ` cvs-commit at gcc dot gnu.org [this message] 2020-05-01 1:19 ` amodra at gmail dot com
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-94145-4-FozUcuTJbU@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).