public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65342] [5 Regression] FAIL: gfortran.dg/intrinsic_(un)?pack_1.f90 -O1 execution test on powerpc-apple-darwin9 after r210201 Date: Tue, 10 Mar 2015 13:33:00 -0000 [thread overview] Message-ID: <bug-65342-4-lnJUe42LeN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65342-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65342 --- Comment #9 from Alan Modra <amodra at gmail dot com> --- As far as fixing the real underlying problem goes, I'm not so familiar with the darwin support that I can state with certainty that you need to fix movdi_low and friends. It might help to explain why powerpc64-linux -mcmodel=medium code doesn't hit the intrinsic_unpack problem even though the resultant code looks very similar to darwin code. We don't see a similar propagation of offset into memory load because legitimate_addres_p() says that isn't valid. It isn't valid because legitimate_constant_pool_address_p (also handles toc-relative medium model addresses) checks alignment. So fwprop and combine don't create the problem memory loads in the first place. However, if we did see such a memory load, reload would fix it for us due to the predicate and constraints in movdi_internal64. Note that having legitimate_address_p() prevent these addresses does mean we lose some optimization opportunites, but on the other hand, if we allowed everything early we'd end up with lots of reloads and probably worse code. You may be able to do something similar in legitimate_address_p for darwin.
next prev parent reply other threads:[~2015-03-10 13:33 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-07 10:01 [Bug target/65342] New: " dominiq at lps dot ens.fr 2015-03-07 13:27 ` [Bug target/65342] " amodra at gmail dot com 2015-03-07 13:40 ` dominiq at lps dot ens.fr 2015-03-07 16:55 ` iains at gcc dot gnu.org 2015-03-09 12:16 ` rguenth at gcc dot gnu.org 2015-03-09 14:31 ` jakub at gcc dot gnu.org 2015-03-10 8:22 ` amodra at gmail dot com 2015-03-10 8:44 ` iains at gcc dot gnu.org 2015-03-10 12:44 ` amodra at gmail dot com 2015-03-10 12:59 ` iains at gcc dot gnu.org 2015-03-10 13:13 ` iains at gcc dot gnu.org 2015-03-10 13:33 ` amodra at gmail dot com [this message] 2015-03-10 13:36 ` amodra at gmail dot com 2015-03-16 9:38 ` iains at gcc dot gnu.org 2015-03-16 12:02 ` amodra at gmail dot com 2015-03-16 12:09 ` iains at gcc dot gnu.org 2015-03-25 14:32 ` dominiq at lps dot ens.fr 2015-04-09 10:13 ` iains at gcc dot gnu.org 2015-04-09 10:41 ` dominiq at lps dot ens.fr 2015-04-22 12:00 ` [Bug target/65342] [5/6 " jakub at gcc dot gnu.org 2015-07-16 9:17 ` rguenth 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-65342-4-lnJUe42LeN@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).