From: Andrew Macleod <amacleod@cygnus.com>
To: amacleod@redhat.com, dje@watson.ibm.com
Cc: gcc@gcc.gnu.org
Subject: Re: initialize_uninitialized_subregs causing bootstrap failure
Date: Wed, 05 Dec 2001 12:55:00 -0000 [thread overview]
Message-ID: <200112052054.MAA16717@rtl.cygnus.com> (raw)
>>
>> * rtl.h (initialize_uninitialized_subregs): New prototype.
>> * toplev.c (rest_of_compilation): Call initialize_uninitialized_subregs
>> when optimization is on.
>> * flow.c (find_regno_partial): Find subregs within an expression.
>> (initialize_uninitialized_subregs): Initialize live on entry registers
>> which are used in subreg expressions.
>>
>> is causing bootstrap to fail on AIX when compiling in 64-bit mode:
>>
>> ./xgcc -B./ -B/gcc/dje/install/powerpc-ibm-aix4.3.3.0-20011205/powerpc-ibm-aix4.3.3.0/bin/ -isystem /gcc/dje/install/powerpc-ibm-aix4.3.3.0-20011205/powerpc-ibm-aix4.3.3.0/include -isystem /gcc/dje/install/powerpc-ibm-aix4.3.3.0-20011205/powerpc-ibm-aix4.3.3.0/sys-include -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -g1 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I/gcc/dje/src/gcc -I/gcc/dje/src/gcc/. -I/gcc/dje/src/gcc/config -I/gcc/dje/src/gcc/../include -maix64 -DL_muldi3 -c /gcc/dje/src/gcc/libgcc2.c -o libgcc/ppc64/_muldi3.o
>> /gcc/dje/src/gcc/libgcc2.c: In function `__muldi3':
>> /gcc/dje/src/gcc/libgcc2.c:367: unrecognizable insn:
>> (insn 81 75 4 (set (zero_extract:DI (reg/v:DI 121)
>> (const_int 32 [0x20])
>> (const_int 0 [0x0]))
>> (const_int 0 [0x0])) -1 (nil)
>> (nil))
>> /gcc/dje/src/gcc/libgcc2.c:367: Internal compiler error in extract_insn, at recog.c:2128
>>
>> This is the stage1 compiler which is failing.
>>
>> Please fix this ASAP or revert the patch.
>>
urg. See if this helps, if so, I'll check it in.... It looks like I checked in the
n-1 version of the patch somehow... (which also bootstrapped on 2 targets...)
Andrew
* flow.c (find_regno_partial): Return register, not the expression
the register is in.
Index: flow.c
===================================================================
RCS file: /cvs/gcc/egcs/gcc/flow.c,v
retrieving revision 1.494
diff -c -p -r1.494 flow.c
*** flow.c 2001/12/05 01:39:41 1.494
--- flow.c 2001/12/05 20:50:13
*************** find_regno_partial (ptr, data)
*** 1327,1333 ****
case STRICT_LOW_PART:
if (GET_CODE (XEXP (*ptr, 0)) == REG && REGNO (XEXP (*ptr, 0)) == reg)
{
! param->retval = *ptr;
return 1;
}
break;
--- 1327,1333 ----
case STRICT_LOW_PART:
if (GET_CODE (XEXP (*ptr, 0)) == REG && REGNO (XEXP (*ptr, 0)) == reg)
{
! param->retval = XEXP (*ptr, 0);
return 1;
}
break;
*************** find_regno_partial (ptr, data)
*** 1336,1342 ****
if (GET_CODE (SUBREG_REG (*ptr)) == REG
&& REGNO (SUBREG_REG (*ptr)) == reg)
{
! param->retval = *ptr;
return 1;
}
break;
--- 1336,1342 ----
if (GET_CODE (SUBREG_REG (*ptr)) == REG
&& REGNO (SUBREG_REG (*ptr)) == reg)
{
! param->retval = SUBREG_REG (*ptr);
return 1;
}
break;
next reply other threads:[~2001-12-05 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 12:55 Andrew Macleod [this message]
2001-12-05 13:11 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2001-12-05 12:42 David Edelsohn
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=200112052054.MAA16717@rtl.cygnus.com \
--to=amacleod@cygnus.com \
--cc=amacleod@redhat.com \
--cc=dje@watson.ibm.com \
--cc=gcc@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).