public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at breakpoint dot cc" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44364] Wrong code with e500 double floating point
Date: Wed, 09 Jun 2010 07:54:00 -0000	[thread overview]
Message-ID: <20100609075400.13422.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44364-14399@http.gcc.gnu.org/bugzilla/>



------- Comment #38 from gcc at breakpoint dot cc  2010-06-09 07:54 -------
(In reply to comment #28)
> Please bootstrap and test this addition to e500.h
> 
> /* When setting up caller-save slots (MODE == VOIDmode) ensure we
>    allocate space for DFmode.  Save gprs in the correct mode too.  */
> #define HARD_REGNO_CALLER_SAVE_MODE(REGNO, NREGS, MODE) \
>   (TARGET_E500_DOUBLE && ((MODE) == VOIDmode || (MODE) == DFmode)       \
>    ? DFmode                                                             \
>    : choose_hard_reg_mode ((REGNO), (NREGS), false))
> 

Okay. Now I found something: 

inst/bin/powerpc-linux-gnuspe-gcc extract_chmLib.i -o extract_chmLib.S -S -O2
extract_chmLib.c: In function '_extract_callback':
extract_chmLib.c:29: internal compiler error: in change_address_1, at
emit-rtl.c:1954
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

extract_chmLib.i is attached. Adding -mfloat-gprs=single which avoids using
64bit gprs for double makes this go away.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44364


  parent reply	other threads:[~2010-06-09  7:54 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 13:42 [Bug rtl-optimization/44364] New: " gcc at breakpoint dot cc
2010-06-01 13:42 ` [Bug rtl-optimization/44364] " gcc at breakpoint dot cc
2010-06-01 13:43 ` gcc at breakpoint dot cc
2010-06-03 19:26 ` [Bug target/44364] " Kyle dot D dot Moffett at boeing dot com
2010-06-03 20:09 ` Kyle dot D dot Moffett at boeing dot com
2010-06-03 20:17 ` gcc at breakpoint dot cc
2010-06-03 20:21 ` Kyle dot D dot Moffett at boeing dot com
2010-06-03 20:22 ` Kyle dot D dot Moffett at boeing dot com
2010-06-03 20:22 ` Kyle dot D dot Moffett at boeing dot com
2010-06-03 20:23 ` Kyle dot D dot Moffett at boeing dot com
2010-06-03 20:26 ` Kyle dot D dot Moffett at boeing dot com
2010-06-03 20:26 ` Kyle dot D dot Moffett at boeing dot com
2010-06-03 23:18 ` Kyle dot D dot Moffett at boeing dot com
2010-06-04  1:37 ` Kyle dot D dot Moffett at boeing dot com
2010-06-04  1:37 ` Kyle dot D dot Moffett at boeing dot com
2010-06-04  2:17 ` Kyle dot D dot Moffett at boeing dot com
2010-06-04  2:17 ` Kyle dot D dot Moffett at boeing dot com
2010-06-04 17:24 ` Kyle dot D dot Moffett at boeing dot com
2010-06-04 17:24 ` Kyle dot D dot Moffett at boeing dot com
2010-06-06 14:11 ` amodra at gmail dot com
2010-06-06 14:52 ` amodra at gmail dot com
2010-06-06 15:37 ` Kyle dot D dot Moffett at boeing dot com
2010-06-07  4:42 ` amodra at gmail dot com
2010-06-07  5:36 ` Kyle dot D dot Moffett at boeing dot com
2010-06-07  5:44 ` Kyle dot D dot Moffett at boeing dot com
2010-06-07  9:53 ` amodra at gmail dot com
2010-06-07 10:30 ` amodra at gmail dot com
2010-06-07 12:49 ` Kyle dot D dot Moffett at boeing dot com
2010-06-07 17:06 ` amodra at gmail dot com
2010-06-07 18:28 ` Kyle dot D dot Moffett at boeing dot com
2010-06-07 18:56 ` Kyle dot D dot Moffett at boeing dot com
2010-06-08  4:24 ` Kyle dot D dot Moffett at boeing dot com
2010-06-08  5:08 ` Kyle dot D dot Moffett at boeing dot com
2010-06-08  6:48 ` Kyle dot D dot Moffett at boeing dot com
2010-06-08 11:24 ` gcc at breakpoint dot cc
2010-06-08 15:23 ` Kyle dot D dot Moffett at boeing dot com
2010-06-08 20:34 ` Kyle dot D dot Moffett at boeing dot com
2010-06-09  7:51 ` gcc at breakpoint dot cc
2010-06-09  7:54 ` gcc at breakpoint dot cc [this message]
2010-06-09  8:59 ` harry dot he at freescale dot com
2010-06-09  9:23 ` harry dot he at freescale dot com
2010-06-09 13:26 ` amodra at gmail dot com
2010-06-09 13:53 ` gcc at breakpoint dot cc
2010-06-09 14:07 ` mark dot workman at acm dot org
2010-06-10  9:03 ` harry dot he at freescale dot com
2010-06-10 17:43 ` mark dot workman at acm dot org
2010-06-11  1:09 ` harry dot he at freescale dot com
2010-06-21 15:56 ` Kyle dot D dot Moffett at boeing dot com
2010-06-22 10:44 ` amodra at gcc dot gnu dot org
2010-06-28 11:19 ` gcc at breakpoint dot cc
     [not found] <bug-44364-4@http.gcc.gnu.org/bugzilla/>
2013-02-07  1:44 ` 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=20100609075400.13422.qmail@sourceware.org \
    --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: link
Be 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).