From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: daniel tian <daniel.xntian@gmail.com>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
gcc@gcc.gnu.org, Ian Lance Taylor <iant@google.com>,
peng.zheng@mavrixtech.com
Subject: Re: DImode operations
Date: Mon, 28 Sep 2009 13:07:00 -0000 [thread overview]
Message-ID: <4AC0B71C.8000502@gmail.com> (raw)
In-Reply-To: <121fadb80909280239n4c3419afic2baaea3b9a3cd66@mail.gmail.com>
daniel tian wrote:
> ../../../rice-gcc-4.3.0/libgcc/../gcc/libgcc2.c: In function '__muldi3':
> ../../../rice-gcc-4.3.0/libgcc/../gcc/libgcc2.c:557: internal compiler
> error: in emit_move_insn, at expr.c:3379
> make[2]: *** [_muldi3.o] Error 1
> gcc_assert (mode != BLKmode
> && (GET_MODE (y) == mode || GET_MODE (y) == VOIDmode));
>
> in function emit_move_insn cause the error. Because the machine mode
> in rtx x, y are different. X is SImode, while y is DImode.
Well, you need to establish why this insn is being generated. Is it coming
from your expanders perhaps? Now that you've figured out debugging cc1, set a
breakpoint on "internal_compiler_error" and take a look at the backtrace to
see what function has called emit_move_insn; the answer probably lies there.
cheers,
DaveK
next prev parent reply other threads:[~2009-09-28 13:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 11:10 daniel tian
2009-09-23 13:02 ` Dave Korn
2009-09-24 7:05 ` daniel tian
2009-09-24 9:01 ` daniel tian
2009-09-24 14:54 ` Dave Korn
2009-09-28 10:50 ` daniel tian
2009-09-28 11:44 ` daniel tian
2009-09-28 13:07 ` Dave Korn [this message]
2009-09-29 2:00 ` daniel tian
2009-09-29 6:50 ` daniel tian
2009-09-29 14:56 ` Ian Lance Taylor
2009-09-30 12:39 ` daniel tian
2009-09-24 14:49 ` Dave Korn
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=4AC0B71C.8000502@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=daniel.xntian@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=peng.zheng@mavrixtech.com \
/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).