public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dbaird at nmt dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/16925] ICE when building a m68hc11 cross-compiler on 64-bit architectures Date: Wed, 22 Dec 2004 07:13:00 -0000 [thread overview] Message-ID: <20041222071334.5054.qmail@sourceware.org> (raw) In-Reply-To: <20040808232347.16925.aurelien@aurel32.net> ------- Additional Comments From dbaird at nmt dot edu 2004-12-22 07:13 ------- Just for the record, I am having the same problem. I am using GCC as the host compiler. My CHOST is x86_64-pc-linux-gnu. I am building gcc-3.3.4 with patches from (Pre-Release 2.92): http://m68hc11.serveftp.org/m68hc1x-builder-2.92.tar.gz Compilation succeeds after I apply gcc-3.4.2-16925.patch from above. (In reply to comment #3) > Created an attachment (id=7096) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=7096&action=view) > Patch to fix that bug > > The first part of the patch adds the fact that CONST_INT could be a DImode rtx, > that needs to be split into two SImode rtx. > > The second part fixes the core of the bug. On 32-bit hosts, this part is called > when a 32-bit integer has two be split into two 32-bit integers (CONST_INT is a > 32-bit integer on 32-bit hosts, as well as SI mode). The problem is that > CONST_INT is a 64-bit integer on 64-bit hosts. > > Actually this condition is always false on 32-bit hosts (a grep for > split_logical shows that the operands is always a DImode when mode == SImode). > This should also be always false on 64-bit hosts, that's why I removed that > code. > > I don't understand why that code is trying to convert one SImode rtx into two > SImode rtx, moreover in a function whose name is beginning by split. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16925
next prev parent reply other threads:[~2004-12-22 7:13 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-08 23:23 [Bug c/16925] New: ICC " aurelien at aurel32 dot net 2004-08-08 23:24 ` [Bug c/16925] " aurelien at aurel32 dot net 2004-08-08 23:38 ` [Bug target/16925] " pinskia at gcc dot gnu dot org 2004-08-11 22:25 ` aurelien at aurel32 dot net 2004-09-11 13:36 ` aurelien at aurel32 dot net 2004-09-11 14:29 ` [Bug target/16925] ICE " schwab at suse dot de 2004-12-22 7:13 ` dbaird at nmt dot edu [this message] 2004-12-22 7:20 ` pinskia at gcc dot gnu dot org 2004-12-22 9:15 ` aurelien at aurel32 dot net 2005-01-28 20:34 ` ciceron at gcc dot gnu dot org 2005-05-08 10:09 ` cvs-commit at gcc dot gnu dot org 2005-05-08 10:15 ` cvs-commit at gcc dot gnu dot org 2005-05-08 10:24 ` cvs-commit at gcc dot gnu dot org 2005-05-08 10:29 ` ciceron at gcc dot gnu dot org 2005-05-08 15:34 ` pinskia at gcc dot gnu dot 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=20041222071334.5054.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: 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).