public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: daniel tian <daniel.xntian@gmail.com>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: gcc@gcc.gnu.org, peng.zheng@mavrixtech.com
Subject: Re: DImode operations
Date: Tue, 29 Sep 2009 06:50:00 -0000	[thread overview]
Message-ID: <121fadb80909282050h339a6e11i60abf207db41f850@mail.gmail.com> (raw)
In-Reply-To: <121fadb80909281843p63374a09rc1be2b4ebade6858@mail.gmail.com>

Hi Dave:

when I build the libgcc2.c, an unrecognizable RTL exist. Its about subreg.
Here is the info:

../../../rice-gcc-4.3.0/libgcc/../gcc/libgcc2.c: In function '__mulvsi3':
../../../rice-gcc-4.3.0/libgcc/../gcc/libgcc2.c:169: error: unrecognizable insn:
(insn 24 26 25 3 ../../../rice-gcc-4.3.0/libgcc/../gcc/libgcc2.c:165
(set (subreg:SI (reg:DI 47) 0)
        (ashiftrt:SI (subreg:SI (reg/v:DI 36 [ w ]) 4)
            (const_int 0 [0x0]))) -1 (expr_list:REG_NO_CONFLICT
(reg/v:DI 36 [ w ])
        (nil)))
../../../rice-gcc-4.3.0/libgcc/../gcc/libgcc2.c:169: internal compiler
error: in extract_insn, at recog.c:1990

I could understand why subreg exist, but gcc supposed to deal with it.
I mean to remove the subreg operations.

Did your guys also meet this problem?

Could you give me some advices?
Now I still debug it.

Thanks.

  reply	other threads:[~2009-09-29  3:50 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
2009-09-29  2:00             ` daniel tian
2009-09-29  6:50               ` daniel tian [this message]
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=121fadb80909282050h339a6e11i60abf207db41f850@mail.gmail.com \
    --to=daniel.xntian@gmail.com \
    --cc=dave.korn.cygwin@googlemail.com \
    --cc=gcc@gcc.gnu.org \
    --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).