public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Internal Error compiling ddd
Date: Mon, 24 Jul 2000 19:55:22 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205227@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205226@msgid-missing>

	BoxPoint.h:1352: Internal compiler error in `fix_lexical_addr', at
	function.c:5409

Probably a known bug with the C++ front end in the February (000216)
toolchain.  I'd suggest trying different optimization options -O1 or -O0.

The February toolchain is based on an FSF snapshot from Jan 3, and there were
unfortuntely some instabilities in the C++ front end at that time due to
C++ front end development.  These bugs have all been fixed long ago.  But
since they were fixed by additional C++ front end development, the patches
aren't really suitable for a released toolchain.

I think the best fix for this is to make a new release, and hope that the new
release has a more stable C++ front end.  Unfortunately, this is likely to
continue to be a problem until the FSF makes a release, since there continues
to be a lot of development work going into the C++ front end and other parts
of gcc.

Red Hat is working on a new toolchain release for the ia64-linux project.  We
made a CVS branch for the release last Monday, based on the July 10 FSF gcc
snapshot, and we are now testing the compiler and fixing bugs.  I could make
a pre-release at any time, but I think we need to fix a couple of more bugs
before that will be really useful.

Jim



  reply	other threads:[~2000-07-24 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-24 19:41 [Linux-ia64] Internal Error compiling ddd Michael Madore
2000-07-24 19:55 ` Jim Wilson [this message]
2000-07-26 19:29 ` H . J . Lu
2000-07-27  0:02 ` Jim Wilson

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=marc-linux-ia64-105590678205227@msgid-missing \
    --to=wilson@cygnus.com \
    --cc=linux-ia64@vger.kernel.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