target/5107: ICE when building an ARM/Thumb cross compiler for/on HP-UX.

[Richard Earnshaw]

The following reply was made to PR target/5107; it has been noted by GNATS.

From: Richard Earnshaw <rearnsha@arm.com>
To: Klaus Pedersen <klaus.k.pedersen@nokia.com>
Cc: Richard.Earnshaw@arm.com, gcc-gnats@gcc.gnu.org
Subject: Re: target/5107: ICE when building an ARM/Thumb cross compiler 
 for/on HP-UX.
Date: Fri, 14 Dec 2001 18:06:10 +0000

 > Yes, it seems you are right, I tried this program:
 > 
 > 	long __muldi3(void)
 > 	{
 > 		return 65536;
 > 	}
 > - and even this simple program generates the ICE.
 
 OK, that reduces the problem a bit, and confirms my basic suspicions.
 
 > Does the error have any connection to these warnings that is generated
 > when parsing the arm.md file? (there are some references to 
 > define_split)
 > ---
 > ./genrecog ../../gcc-20011203/gcc/config/arm/arm.md > tmp-recog.c
 > ../../gcc-20011203/gcc/config/arm/arm.md:595: warning: constraints not
 > supported in define_peephole2
 
 This isn't related to your problem.
 
 > How do I force configure to use the native compiler? Is it enough to
 > set the CC enviroment variable before configuring?
 
 Yes, set the CC environment variable; but,
 
 > 
 > OK, it seems that we don't have a native ANSI compiler, the "bundled C
 > compiler" stops at the first ANSI construct, function prototypes!
 > 
 > How can HP get away with that?
 
 Good question.  I think HP's response will be something along the lines of
 
 "That compiler is only intended for those people who need to customise and 
 link a new kernel for their particular machine."
 > 
 > Besides this try, I have only used gcc. This is a selection:
 > 
 
 OK.  I strongly suspect a bug in your native (HPUX) GCC, which is causing 
 a miscompilation of the ARM code, though it is a little surprising that so 
 many variants should all produce similar effects.