From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Internal Error compiling ddd
Date: Thu, 27 Jul 2000 00:02:27 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205232@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205226@msgid-missing>
I am aware of your messages on this subject to the FSF gcc mailing lists.
However, none of your messages actually report any bugs. You just claim
that bugs exist and propose solutions for them. Your proposed solutions
involve a redesign of gcc, are highly controversial, and very unlikely to be
adopted anytime soon. Thus I am in a position where I can't fix anything
because I don't have anything to work with.
As I understand it, glibc needs to know about frame_object which is a gcc
internal variable. The gcc hackers didn't know about this until you pointed
it out. frame_object had to be changed in gcc to support the Intel defined
IA-64 exception handling model. Thus glibc will have to be changed to match
the gcc changes. I see nothing in gcc to fix. Since I'm not doing glibc
work, you need to report this to one of the glibc maintainers, e.g. Jes or
Ulrich, and ask them to fix glibc. Perhaps this work has already been done
for glibc 2.2, I don't know. If so, then there is nothing left to fix.
glibc 2.1.3 and the current FSF gcc sources would still be broken, but it
has never been anyone's intent to make that work. You should be using the
February (000216) release with glibc 2.1.3.
Jim
prev parent reply other threads:[~2000-07-27 0:02 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
2000-07-26 19:29 ` H . J . Lu
2000-07-27 0:02 ` Jim Wilson [this message]
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-105590678205232@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