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: [Linux-ia64] Re: ia64 toolchain problem
Date: Mon, 31 Jul 2000 18:56:48 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205249@msgid-missing> (raw)

I still don't know what bug you are trying to report.  If indeed there is a
bug here, I would very much like to know what it is.

I agree that there is a discrepancy between glibc and gcc.  Obviously, we need
to fix glibc to match gcc.  Your proposal to change gcc to avoid future
problems has some merit, but it is very controversial and unlikely to be
adopted anytime soon.  If you can wait a year for a fix, then fine, we can go
with the gcc change.  Otherwise, if you want the problem fixed now, then we
need to fix glibc.  Like I said last time, you need to report this bug to the
glibc maintainers so that they can fix glibc.

	My point is gcc should define a stable ABI

There is no stable ABI yet, because we are still writing the compiler.
When the compiler is done, the ABI will be stable, and we won't have this
problem anymore.

These are the kinds of problems you have to live with when the hardware, OS,
and compilers are all developed in parallel.

	Is collect2 used on ia64?  If yes, it has the same problem as glibc

Yes and no.  collect2 does multiple things, and is used for all targets.
But the important bit here, creating the init sections, is not used for most
elf targets including ia64, and hence this isn't a problem.

Jim



                 reply	other threads:[~2000-07-31 18:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-105590678205249@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