public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/45585] [4.6 Regression] ICE on powerpc-apple-darwin9 for gfortran.dg/transfer_simplify_2.f90 with -O2 -m64 Date: Fri, 05 Nov 2010 21:29:00 -0000 [thread overview] Message-ID: <bug-45585-4-dLUBCP0zVA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-45585-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45585 Michael Meissner <meissner at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot |meissner at gcc dot gnu.org |gnu.org | --- Comment #5 from Michael Meissner <meissner at gcc dot gnu.org> 2010-11-05 21:28:55 UTC --- Created attachment 22297 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22297 Patch to allow loading/storing DI values in FPR registers This patch fixes the problem in the bug. What is happening is originally if you were loading up a static 64-bit integer variable to convert it to floating point, the compiler would first load the variable into a GPR, then store it on the stack, and then load the value from the stack to the FPR. My optimization allowed the fp convert to take memory operands so it didn't have to go through the GPR registers. However, since Darwin has its own patterns for load/store, it didn't go through the normal move patterns, and was overlooked.
next prev parent reply other threads:[~2010-11-05 21:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-45585-4@http.gcc.gnu.org/bugzilla/> 2010-09-30 15:37 ` rguenth at gcc dot gnu.org 2010-10-10 19:38 ` dominiq at lps dot ens.fr 2010-11-04 22:00 ` dominiq at lps dot ens.fr 2010-11-05 21:29 ` meissner at gcc dot gnu.org [this message] 2010-11-05 21:31 ` meissner at gcc dot gnu.org 2010-11-07 11:45 ` dominiq at lps dot ens.fr 2010-11-08 19:02 ` meissner at gcc dot gnu.org 2010-11-08 19:04 ` meissner 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-45585-4-dLUBCP0zVA@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).