public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/5107: ICE when building an ARM/Thumb cross compiler  for/on HP-UX.
Date: Fri, 14 Dec 2001 10:16:00 -0000	[thread overview]
Message-ID: <20011214181602.11714.qmail@sources.redhat.com> (raw)

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.
 
 
 


             reply	other threads:[~2001-12-14 18:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-14 10:16 Richard Earnshaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15  3:14 rearnsha
2002-03-04 17:36 Craig Rodrigues
2001-12-17  6:36 Klaus Pedersen
2001-12-17  2:36 Klaus Pedersen
2001-12-15  8:46 Richard Earnshaw
2001-12-14  9:56 Klaus Pedersen
2001-12-14  2:56 Richard Earnshaw
2001-12-13 14:46 Klaus.k.pedersen

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=20011214181602.11714.qmail@sources.redhat.com \
    --to=rearnsha@arm.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).